<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
  <head>
    <meta name="author" content="Paul Bender" />
    <meta name="copyright" content="2006-2008 Paul Bender &amp; minimyth.org" />
    <meta name="keywords" content="Minimyth,Linux,PVR,Linux,MythTV,diskless,Mini-ITX,ION,ION1,ION2,NUC" />
    <meta name="description" content="" />
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <title>Minimyth - Documents - minimyth.conf description</title>
    <style type="text/css" title="main-styles">
      @import "css/minimyth.css";
    </style>
  </head>
  <body>
    <div class="main">
      <div class="header">
        <div class="heading">MiniMyth2</div>
        <div class="menu">
          <span class="menuItem"><a href="index.html">Home</a></span>
          <span class="menuItem"><a href="document.html">Documents</a></span>
          <span class="menuItem">minimyth.conf</span>
        </div>
      </div>
      <div class="middle">
        <div class="heading">minimyth.conf description</div>
        <div id="toc" class="section">
          <div class="heading">Table of contents</div>
          <ul>
            <li><a href="#general">General</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MINIMYTH">Configuration variables for: Minimyth</a></li>
            <li><a href="#MM_DHCP">Configuration variables for: DHCP override</a></li>
            <li><a href="#MM_SECURITY">Configuration variables for: security</a></li>
            <li><a href="#MM_ACPI">Configuration variables for: ACPI</a></li>
            <li><a href="#MM_CPU">Configuration variables for: CPU</a></li>
            <li><a href="#MM_AUDIO">Configuration variables for: audio</a></li>
            <li><a href="#MM_VIDEO">Configuration variables for: video</a></li>
            <li><a href="#MM_X">Configuration variables for: X</a></li>
            <li><a href="#MM_FONT">Configuration variables for: fonts</a></li>
            <li><a href="#MM_MAIL">Configuration variables for: mail notifications via OSD</a></li>
            <li><a href="#MM_MASTER">Configuration variables for: Myth master backend communication</a></li>
            <li><a href="#MM_MEDIAPLAYERS">Configuration variables for: mediaplayers</a></li>
            <li><a href="#MM_MYTH">Configuration variables for: mythtv</a></li>
            <li><a href="#MM_PLUGIN">Configuration variables for: Myth plugins</a></li>
            <li><a href="#MM_EXTRAS">Configuration variables for: extras directory</a></li>
            <li><a href="#MM_CODECS">Configuration variables for: CODECs directory</a></li>
            <li><a href="#MM_FLASH">Configuration variables for: Adobe Flash Player</a></li>
            <li><a href="#MM_THEME">Configuration variables for: themes</a></li>
            <li><a href="#MM_MEDIA">Configuration variables for: remote media directories</a></li>
            <li><a href="#MM_GAME">Configuration variables for: games</a></li>
            <li><a href="#MM_LIRC">Configuration variables for: LIRC</a></li>
            <li><a href="#MM_LCDPROC">Configuration variables for: LCDproc</a></li>
            <li><a href="#MM_EXTERNAL">Configuration variables for: external equipment control</a></li>
            <li><a href="#MM_SSH_SERVER">Configuration variables for: SSH server</a></li>
            <li><a href="#MM_CRON">Configuration variables for: cron</a></li>
            <li><a href="#MM_MYTHDB">Configuration variables for: Myth frontend</a></li>
            <li><a href="#MM_LMSENSORS">Configuration variables for: lmsensors</a></li>
            <li><a href="#MM_MAKEMKV">Configuration variables for: optical disc ripping/copy</a></li>
            <li><a href="#MM_VOIP">Configuration variables for: VoIP telephony</a></li>
          </ul>
        </div>
        <div id="general" class="section">
          <div class="heading">General</div>
          <p>
            The MiniMyth2 configuration file 'minimyth.conf" is at the core of the MiniMyth2 configuration process.
            The goal is for all MiniMyth2 configuration to be done with the MiniMyth2 configuration file.
            Since this is sometimes not possible today, MiniMyth2 provides other configuration methods as well.
            However, the need to use any of these other configuration methods should be considered a bug.
            Therefore, if you need to use these other configuration methods, then
            <a href="http://minimyth2.freeforums.org">let us know</a>.
          </p>
          <p>
            Essentially, the MiniMyth2 configuration file variables are shell variables.
            In fact, MiniMyth2 configuration variables are processed using the shell.
            Therefore, all variable values should be enclosed in single quotes (')
            to prevent the shell from interpreting the values.
            Therefore, all MiniMyth2 configuration file settings should take the form:
          </p>
          <p>
            {variable-name}='{variable-value}'
          </p>
        </div>
        <div id="MM_MINIMYTH" class="section">
          <div class="heading">Configuration variables for: MiniMyth2</div>
          <ul>
            <li><a href="#MM_MINIMYTH-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MINIMYTH_BOOT_URL">MM_MINIMYTH_BOOT_URL</a></li>
            <li><a href="#MM_MINIMYTH_FETCH_MINIMYTH_SCRIPT">MM_MINIMYTH_FETCH_MINIMYTH_SCRIPT</a></li>
            <li><a href="#MM_MINIMYTH_LOGROTATE">MM_MINIMYTH_LOGROTATE</a></li>
            <li><a href="#MM_AVAHI_ENABLED">MM_AVAHI_ENABLED</a></li>
            <li><a href="#MM_FETCH_SSH_CLIENT_RSA_KEY">MM_FETCH_SSH_CLIENT_RSA_KEY</a></li>
            <li><a href="#MM_FETCH_UI_LOCALIZATIONS">MM_FETCH_UI_LOCALIZATIONS</a></li>
            <li><a href="#MM_NOTIFY_ABOUT_UPDATES">MM_NOTIFY_ABOUT_UPDATES</a></li>
            <li><a href="#MM_RESTART_NTP_ON_SLEEP">MM_RESTART_NTP_ON_SLEEP</a></li>
            <li><a href="#MM_SWAP_ENABLED">MM_SWAP_ENABLED</a></li>
          </ul>
          <dl>
            <dt id="MM_MINIMYTH-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                General MiniMyth2 related configuration variables.
              </p>
              <p>
                The
                <a href="http://en.wikipedia.org/wiki/Uniform_Resource_Locator">Uniform Resource Locators (URLs)</a>
                in this section must have the following form:
              </p>
              <p>
                {protocol}://{server}/{path}
              </p>
              <p>
                The valid protocol values are: 'http", 'tftp' and 'file'.
              </p>
            </dd>
            <dt id="MM_MINIMYTH_BOOT_URL"><strong>MM_MINIMYTH_BOOT_URL</strong></dt>
            <dd>
              <p>
                Set the MiniMyth2 boot directory.
                MiniMyth2 needs to know the boot directory because the
                <a href="document-configure.html#location">location of configuration files</a>
                is relative to the boot directory.
              </p>
              <p>
                If MM_MINIMYTH_BOOT_URL is not set,
                then MiniMyth2 'guesses' the boot directory using other information as described in the
                <a href="document-configure.html#location">location of configuration files</a>
                section.
                However, you may want to override the guessed boot directory
                when MiniMyth2 'guesses' the wrong boot directory or
                when MiniMyth2 'guesses' the right boot directory
                but you want to use a different protocol to access the boot directory.
              </p>
              <p>
                If MM_MINIMYTH_BOOT_URL is set on the
                <a href="document-configure.html#bootline">boot line</a>,
                then MiniMyth2 will use the value as the boot directory when retrieving all configuration files.
                If MM_MINIMYTH_BOOT_URL is set on in the
                <a href="document-configure.html#minimyth_conf">MiniMyth2 configuration file</a>
                then MiniMyth2 will use the value as the boot directory when retrieving all configuration files except the
                <a href="document-configure.html#minimyth_conf">MiniMyth2 configuration file</a>,
                and will use the 'guessed' boot directory as the boot directory when retrieving the
                <a href="document-configure.html#minimyth_conf">MiniMyth2 configuration file</a>.
              </p>
              <p>
                I do not like to use the TFTP protocol because it can be slow and unreliable.
                Therefore, I make my TFTP root directory (/var/tftpboot) available as a virtual web host (tftp.home) as well,
                allowing MiniMyth2 to access the configuration files using the root directory URL 'http://tftp.home/MiniMyth2/'.
                Below is the section of my
                <a href="http://httpd.apache.org/">Apache HTTP Server</a>
                configuration file
                that makes my TFTP root directory available as a virtual web host.
              </p>
<pre>
# Load the mod_dav and mod_dav_fs modules needed by the MiniMyth2 read-write configuration directory.
LoadModule dav_module modules/mod_dav.so
LoadModule dav_fs_module modules/mod_dav_fs.so

# Configure the mod_dav_fs module needed by the MiniMyth2 read-write configuration directory.
&lt;IfModule mod_dav_fs.c&gt;
    # Location of the WebDAV lock database.
    DAVLockDB /var/lib/dav/lockdb
&lt;/IfModule&gt;

# Configure a virtual host to serve the TFTP directory.
&lt;VirtualHost 192.168.0.1:80&gt;
    DocumentRoot /var/tftpboot
    ServerName tftp.home
    ServerAdmin webmaster@www.home
    &lt;Directory /var/tftpboot&gt;
        AllowOverride None
    &lt;/Directory&gt;
    &lt;Location /&gt;
        # Do not allow access to the TFTP directory except where explicitly granted.
        Order Deny,Allow
        Deny from all
        Dav Off
        &lt;LimitExcept GET&gt;
        &lt;/LimitExcept&gt;
    &lt;/Location&gt;
    &lt;Location /MiniMyth2&gt;
        # Restrict access to the MiniMyth2 frontends.
        Order Deny,Allow
        Deny from all
        Allow from myth-livingroom.home
        Allow from myth-parents.home
        Allow from myth-sp8000e.home
    &lt;/Location&gt;
    &lt;Location /MiniMyth2/conf&gt;
        # If the file is not in host specific directory, then redirect to the default directory.
        # This gets rid of the page failure messages from the logs and should speed things up somewhat.
        # One downside is that the MiniMyth2 logs will show that the file came from the host specfic directory
        # even though the file is located in the default directory.
        RewriteEngine on
        RewriteCond %{REQUEST_FILENAME} !^.+/default/[^/]+$
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteRule ^(.+)/[^/]+/([^/]+)$ $1/default/$2 [L]
    &lt;/Location&gt;
    &lt;Location /MiniMyth2/conf-rw&gt;
        # Turn on WebDAV so that MiniMyth2 can put configuration files.
        # This will not work unless the mod_dav and mod_dav_fs modules are enabled and configured:
        # <a href="http://httpd.apache.org/docs/2.0/mod/mod_dav.html">http://httpd.apache.org/docs/2.0/mod/mod_dav.html</a>
        # and
        # <a href="http://httpd.apache.org/docs/2.0/mod/mod_dav_fs.html">http://httpd.apache.org/docs/2.0/mod/mod_dav_fs.html</a>.
        Dav On
        FileETag None
        &lt;LimitExcept GET PUT&gt;
        &lt;/LimitExcept&gt;
    &lt;/Location&gt;
&lt;/VirtualHost&gt;</pre>
            </dd>
            <dt id="MM_MINIMYTH_FETCH_MINIMYTH_SCRIPT"><strong>MM_MINIMYTH_FETCH_MINIMYTH_SCRIPT</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#minimyth_script">minimyth.script</a>'
                file from the frontend's MiniMyth read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
            <dt id="MM_MINIMYTH_LOGROTATE"><strong>MM_MINIMYTH_LOGROTATE</strong></dt>
            <dd>
              <p>
                Indicate wheter or not log files should be rotate. If enabled, all log files will be 
                rotated every 3 days.
                The default value is 'no'.
              </p>
            </dd>
            <dt id="MM_AVAHI_ENABLED"><strong>MM_AVAHI_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate wheter or not start AVAHI daemon. If enabled, AVAHI daemon will publish telnet and HTTP
                services allowing ZeroConf/ or Bonjur enabled aplications to disscover this frontend for HTTP & Telnet services.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
            </dd>
            <dt id="MM_FETCH_SSH_CLIENT_RSA_KEY"><strong>MM_FETCH_SSH_CLIENT_RSA_KEY</strong></dt>
            <dd>
              <p>
                Indicate wheter or not to fetch SSH client RSA key nededd to access SSH server on backend machine. Such access
                is needed when MiniMyth2 user wants to use OSD backend status function and/or wants to do basic backend maintenace
                from MiniMyth2 GUI. If set to 'yes', MiniMyth2 will download file named 'id_rsa' from conf-ro directory and will
                install it as private SSH RSA key.
                Valid values are 'yes' 'no' and empty, with 'no' the default.
              </p>
            </dd>
            <dt id="MM_FETCH_UI_LOCALIZATIONS"><strong>MM_FETCH_UI_LOCALIZATIONS</strong></dt>
            <dd>
              <p>
                Indicate wheter or not to fetch MiniMyth2 UI localization file. This file contains UI meessages which MiniMyth2 will
                display via OSD notifications like new mail notifications, ongoing recordings, FE/BE hardware status, etc.
                If set to 'yes', MiniMyth2 will download file named 'mm_ui_localizations' from conf-ro directory and will
                used strings from this file durring user OSD notifications.
                Valid values are 'yes' 'no' and empty, with 'no' the default.
              </p>
            </dd>
            <dt id="MM_NOTIFY_ABOUT_UPDATES"><strong>MM_NOTIFY_ABOUT_UPDATES</strong></dt>
            <dd>
              <p>
                Indicate wheter or not to MiniMyth2 should notify  user about new updates. If this variable is set to given 'value',
                MiniMyth2 will notify about new updates 15min after boot/resume (if they are present) and will check every 'value' 
                minutes for new updates. It is resonable to set <value> to something like 360 (6h) for avoiding too frequent checks.
                Valid values are '<value>' and empty, with empty the default.
              </p>
            </dd>
            <dt id="MM_RESTART_NTP_ON_SLEEP"><strong>MM_RESTART_NTP_ON_SLEEP</strong></dt>
            <dd>
              <p>
                Indicate wheter or not to MiniMyth2 should restart NTP daemon across suspend-to-RAM sleep-resume cycle. On some
                systems there is broken kernel-to-NTP notification. By this, after resume, NTP is not immediatelly synchronizing 
                local time. This resulting potential time offset between frontend and backend. This option allows to stop NTP 
                before sleep and restart NTP after resume. 
                Valid values are 'yes' and empty, with empty the default.
              </p>
            </dd>
            <dt id="MM_SWAP_ENABLED"><strong>MM_SWAP_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate wheter or not to MiniMyth2 should create and enable swap to zram devices.
                The zram devices are compressed block devices resifing in RAM and used for swap. If MM_SWAP_ENABLED variable is set to 'yes',
                MiniMyth2 will create set of swap zram devices equal to number of CPU cores with total sum of zram devices size 
                as 1/2 of total avaliable RAM in system.
                Valid values are 'yes' and empty, with 'yes' the default.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_DHCP" class="section">
          <div class="heading">Configuration variables for: DHCP override</div>
          <ul>
            <li><a href="#MM_DHCP-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_DHCP_HOST_NAME">MM_DHCP_HOST_NAME</a></li>
            <li><a href="#MM_DHCP_DOMAIN_NAME">MM_DHCP_DOMAIN_NAME</a></li>
            <li><a href="#MM_DCHP_DOMAIN_NAME_SERVERS">MM_DCHP_DOMAIN_NAME_SERVERS</a></li>
            <li><a href="#MM_DHCP_NTP_SERVERS">MM_DHCP_NTP_SERVERS</a></li>
            <li><a href="#MM_DHCP_LOG_SERVERS">MM_DHCP_LOG_SERVERS</a></li>
            <li><a href="#MM_DHCP_TCODE">MM_DHCP_TCODE</a></li>
          </ul>
          <dl>
            <dt id="MM_DHCP-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Normally, MiniMyth2 obtains certain network and network service configuration parameters from the
                <a href="http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol">Dynamic Host Configuration Protocol (DHCP)</a>
                server.
                However, most of the DHCP servers found in off-the-shelf home routers do not support some or all of these parameters.
                If your DHCP server does not support certain parameters
                (or provides incorrect values for certain parameters),
                then you can use these DHCP override variables to override the parameter values provided by the DHCP server.
              </p>
            </dd>
            <dt id="MM_DHCP_HOST_NAME"><strong>MM_DHCP_HOST_NAME</strong></dt>
            <dd>See <a href="document-configure.html#dhcp-host-name">Host Name</a>.</dd>
            <dt id="MM_DHCP_DOMAIN_NAME"><strong>MM_DHCP_DOMAIN_NAME</strong></dt>
            <dd>See <a href="document-configure.html#dhcp-domain-name">Domain Name</a>.</dd>
            <dt id="MM_DCHP_DOMAIN_NAME_SERVERS"><strong>MM_DCHP_DOMAIN_NAME_SERVERS</strong></dt>
            <dd>See <a href="document-configure.html#dhcp-domain-name-servers">Domain Name Servers</a>.</dd>
            <dt id="MM_DHCP_NTP_SERVERS"><strong>MM_DHCP_NTP_SERVERS</strong></dt>
            <dd>See <a href="document-configure.html#dhcp-ntp-servers">NTP Servers</a>.</dd>
            <dt id="MM_DHCP_LOG_SERVERS"><strong>MM_DHCP_LOG_SERVERS</strong></dt>
            <dd>See <a href="document-configure.html#dhcp-log-servers">Log Servers</a>.</dd>
            <dt id="MM_DHCP_TCODE"><strong>MM_DHCP_TCODE</strong></dt>
            <dd>See <a href="document-configure.html#dhcp-tcode">TCode</a>.</dd>
          </dl>
        </div>
        <div id="MM_SECURITY" class="section">
          <div class="heading">Configuration variables for: security</div>
          <ul>
            <li><a href="#MM_SECURITY-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_SECURITY_ENABLED">MM_SECURITY_ENABLED</a></li>
            <li><a href="#MM_SECURITY_USER_MINIMYTH_UID">MM_SECURITY_USER_MINIMYTH_UID</a></li>
            <li><a href="#MM_SECURITY_USER_MINIMYTH_GID">MM_SECURITY_USER_MINIMYTH_GID</a></li>
            <li><a href="#MM_SECURITY_FETCH_CREDENTIALS_CIFS">MM_SECURITY_FETCH_CREDENTIALS_CIFS</a></li>
            <li><a href="#MM_SECURITY_FETCH_CA_BUNDLE_CRT">MM_SECURITY_FETCH_CA_BUNDLE_CRT</a></li>
          </ul>
          <dl>
            <dt id="MM_SECURITY-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Security related configuration variables.
              </p>
            </dd>
            <dt id="MM_SECURITY_ENABLED"><strong>MM_SECURITY_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not security is enabled.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                When security is enabled, MiniMyth2 disables less secure access.
                That is, MiniMyth2 disables
              </p>
              <ul>
                <li><a href="document-use.html#access-console">Virtual Console access</a>,</li>
                <li><a href="document-use.html#access-telnet">Telnet access</a>,</li>
                <li><a href="document-use.html#access-http">HTTP access</a> to the file system and</li>
                <li><a href="document-use.html#control-vnc">VNC control</a> on an address other than localhost.</li>
              </ul>
              <p>
                Even when security is enabled,
                if MiniMyth2 detects an error during boot,
                then MiniMyth2 enables
                <a href="document-use.html#access-console">virtual console access</a>
                and
                <a href="document-use.html#access-telnet">telnet access</a>.
                This is a serious security hole,
                but users have difficulty debugging when they cannot connect.
              </p>
            </dd>
            <dt id="MM_SECURITY_USER_MINIMYTH_UID"><strong>MM_SECURITY_USER_MINIMYTH_UID</strong></dt>
            <dd>
              <p>
                Set the UID for the user 'minimyth'.
                Valid values are integers between 200 and 32767, with the default being '1000'.
              </p>
              <p>
                If you have configured MiniMyth2 to mount NFS network shares, then being able to specify the UID for the user 'minimyth' can be useful.
                Since the MiniMyth2 GUI runs as user 'minimyth', it accesses network shares as user 'minimyth'.
                Being able to set the UID for the user 'minimyth' enables it to be set to a UID that has the desired access permissions on the NFS network shares.
              </p>
            </dd>
            <dt id="MM_SECURITY_USER_MINIMYTH_GID"><strong>MM_SECURITY_USER_MINIMYTH_GID</strong></dt>
            <dd>
              <p>
                Set the GID for the user 'minimyth'.
                Valid values are integers between 200 and 32767, with the default being '1000'.
              </p>
            </dd>
            <dt id="MM_SECURITY_FETCH_CREDENTIALS_CIFS"><strong>MM_SECURITY_FETCH_CREDENTIALS_CIFS</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#credentials_cifs">credentials_cifs</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                 MiniMyth2 saves this file as '/etc/cifs/credentials_cifs' on the MiniMyth2 frontend.
                 Therefore, in order to use this credentials file when mounting CIFS shares,
                 you need to add the mount option credentials='/etc/cifs/credentials_cifs'.
              </p>
            </dd>
            <dt id="MM_SECURITY_FETCH_CA_BUNDLE_CRT"><strong>MM_SECURITY_FETCH_CA_BUNDLE_CRT</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#ca_bundle_crt">ca-bundle.crt</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                When KDE libraries are included (for use by MythBrowser),
                MiniMyth2 includes this bundle of certificate authority digital certificates in
                the list of certificate authorities trusted by KDE (and, therefore, MythBrowser).
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_ACPI" class="section">
          <div class="heading">Configuration variables for: ACPI</div>
          <ul>
            <li><a href="#MM_ACPI-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_ACPI_EVENT_BUTTON_POWER">MM_ACPI_EVENT_BUTTON_POWER</a></li>
            <li><a href="#MM_ACPI_VIDEO_FLAGS">MM_ACPI_VIDEO_FLAGS</a></li>
            <li><a href="#MM_S3_WORKAROUNDS">MM_S3_WORKAROUNDS</a></li>
            <li><a href="#MM_ACPI_WOL_ENABLED">MM_ACPI_WOL_ENABLED</a></li>
            <li><a href="#MM_ACPI_WOL_INTF">MM_ACPI_WOL_INTF</a></li>
          </ul>
          <dl>
            <dt id="MM_ACPI-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                ACPI related configuration variables.
              </p>
            </dd>
            <dt id="MM_ACPI_EVENT_BUTTON_POWER"><strong>MM_ACPI_EVENT_BUTTON_POWER</strong></dt>
            <dd>
              <p>
                Set the action to take when the frontend's power button is pushed.
                Valid values are 'off', 'sleep' and 'none', with 'off' the default.
              </p>
            </dd>
            <dt id="MM_ACPI_VIDEO_FLAGS"><strong>MM_ACPI_VIDEO_FLAGS</strong></dt>
            <dd>
              <p>
                Set the ACPI video flags ('/proc/sys/kernel/acpi_video_flags').
                Valid values are '0', '1', '2' and '3', with '0' the default.
              </p>
              <p>
                This variable equivalent to the kernel parameter 'acpi_sleep',
                where
              </p>
              <ul>
                <li>'0' corresponds to acpi_sleep="",</li>
                <li>'1' corresponds to acpi_sleep="s3_bios",</li>
                <li>'2' corresponds to acpi_sleep="s3_mode", and</li>
                <li>'3' corresponds to acpi_sleep="s3_bios,s3_mode".</li>
              </ul>
              <p>
                Setting this variable to one of the non-zero values can sometimes enable
                broken video hardware to wake up from sleep (S3) correctly.
                For example, setting MM_ACPI_VIDEO_FLAGS='2' enables the VIA EPIA SP8000E video to wake from sleep (S3) correctly.
                Unfotunately, VIA EPIA SP8000E video playback stutters after wake from sleep (s3)
                unless X is restarted (see <a href="#MM_RESTART_ON_SLEEP">MM_RESTART_ON_SLEEP</a>)
              </p>
              <p>
                If this variable fails to solve the problem, then try
                <a href="#MM_RESTART_ON_SLEEP">MM_RESTART_ON_SLEEP</a>.
              </p>
            </dd>
            <dt id="MM_S3_WORKAROUNDS"><strong>MM_S3_WORKAROUNDS</strong></dt>
            <dd>
              <p>
                Indicate whether MiniMyth2 should do any special actions directly before
                entering Suspend-To-RAM and directly after returning from Suspend-to-RAM.
                This is usefull when used hardware isn't fully suported by MiniMyth2 and
                for proper suspend-resume some actions are nedded i.e. unloading/loading
                kernel modules.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                Actions are defined in 2 shell scripts files located
                in the frontend's MiniMyth2 read-only configuration directory:
              </p>
              <ul>
                <li><a href="document-configure.html#misc">sleep_workarounds.script</a></li>
                <li><a href="document-configure.html#misc">resume_workarounds.script</a></li>
              </ul>
            </dd>
            <dt id="MM_ACPI_WOL_ENABLED"><strong>MM_ACPI_WOL_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether MiniMyth2 should wakeup via LAN WOL.
                Valid values are 'yes'and "no'. If this variale is not defined - LAN WOL is enabled.
              </p>
            </dd>
            <dt id="MM_ACPI_WOL_INTF"><strong>MM_ACPI_WOL_INTF</strong></dt>
            <dd>
              <p>
                Set LAN WOL network interface. Value of this variable is passed
                to
                Valid values are 'string'. If this variale is not defined, eth0 is used.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_CPU" class="section">
          <div class="heading">Configuration variables for: CPU</div>
          <ul>
            <li><a href="#MM_CPU-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_CPU_FREQUENCY_GOVERNOR">MM_CPU_FREQUENCY_GOVERNOR</a></li>
            <li><a href="#MM_CPU_FETCH_MICROCODE_DAT">MM_CPU_FETCH_MICROCODE_DAT</a></li>
          </ul>
          <dl>
            <dt id="MM_CPU-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                CPU related configuration variables.
              </p>
            </dd>
            <dt id="MM_CPU_FREQUENCY_GOVERNOR"><strong>MM_CPU_FREQUENCY_GOVERNOR</strong></dt>
            <dd>
              <p>
                Set the CPU frequency scaling governor.
                Valid values are 'performance', 'powersave', 'ondemand', 'conservative' and 'userspace',
                with 'performance' the default.
              </p>
              <p>
                If 'userspace' is selected, then the 'powernowd' daemon is run to control the CPU speed.
              </p>
            </dd>
            <dt id="MM_CPU_FETCH_MICROCODE_DAT"><strong>MM_CPU_FETCH_MICROCODE_DAT</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#microcode_dat">microcode.dat</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_AUDIO" class="section">
          <div class="heading">Configuration variables for: audio</div>
          <ul>
            <li><a href="#MM_AUDIO-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_AUDIO_TYPE">MM_AUDIO_TYPE</a></li>
            <li><a href="#MM_AUDIO_CARD_NUMBER">MM_AUDIO_CARD_NUMBER</a></li>
            <li><a href="#MM_AUDIO_DEVICE_NUMBER">MM_AUDIO_DEVICE_NUMBER</a></li>
            <li><a href="#MM_AUDIO_RECON_DISP_FOR_RELOAD_ELD">MM_AUDIO_RECON_DISP_FOR_RELOAD_ELD</a></li>
            <li><a href="#MM_AUDIO_FETCH_ASOUND_CONF">MM_AUDIO_FETCH_ASOUND_CONF</a></li>
            <li><a href="#MM_AUDIO_FETCH_ASOUND_STATE">MM_AUDIO_FETCH_ASOUND_STATE</a></li>
            <li><a href="#MM_AUDIO_IN_CARD_NUMBER">MM_AUDIO_IN_CARD_NUMBER</a></li>
            <li><a href="#MM_AUDIO_DEVICE_UCM_PROFILE">MM_AUDIO_DEVICE_UCM_PROFILE</a></li>
            <li><a href="#MM_AUDIO_DEVICE_UCM_COMMAND">MM_AUDIO_DEVICE_UCM_COMMAND</a></li>
          </ul>
          <dl>
            <dt id="MM_AUDIO-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Audio related configuration variables.
              </p>
            </dd>
            <dt id="MM_AUDIO_TYPE"><strong>MM_AUDIO_TYPE</strong></dt>
            <dd>
              <p>
                Set audio type. Valid values are 'analog', 'digital' and 'digital+analog', with 'digital' the default.
              </p>
            </dd>
            <dt id="MM_AUDIO_CARD_NUMBER"><strong>MM_AUDIO_CARD_NUMBER</strong></dt>
            <dd>
              <p>
                Set audio card number. Valid values are 'auto' and any non-negative integer, with 'auto' the default'.
                Since ALSA uses the card number and the card name interchangeably,
                you can specify the card name as listed in directory '/proc/asound/' instead of the card number.
              </p>
              <p>
                If the value is 'auto', then MiniMyth2 will auto configure the audio card number.
                There is no automatic method for determining the correct audio card number needed by ALSA.
                Therefore, MiniMyth2 uses audio card PCI/USB ids indexed lookup table to determine the correct audio card number.
                If your audio card number is not auto-configured to the correct value,
                then
                <a href="http://MiniMyth2.freeforums.org">let us know</a>
                the motherboard vendor and model,
                the output of the commands 'lspci&nbsp;-mn' and 'lsusb', and
                the audio device number that makes the audio work.
              </p>
            </dd>
            <dt id="MM_AUDIO_DEVICE_NUMBER"><strong>MM_AUDIO_DEVICE_NUMBER</strong></dt>
            <dd>
              <p>
                Set audio device number. Valid values are 'auto' and any non-negative integer, with 'auto' the default'.
              </p>
              <p>
                If the value is 'auto', then MiniMyth2 will auto configure the audio device number.
                There is no automatic method for determining the correct audio device number needed by ALSA.
                Therefore, MiniMyth2 uses audio card PCI/USB ids indexed lookup table to determine the correct audio device number.
                If your audio card number is not auto-configured to the correct value,
                then
                <a href="http://MiniMyth2.freeforums.org">let us know</a>
                the motherboard vendor and model,
                the output of the commands 'lspci&nbsp;-mn' and 'lsusb', and
                the audio device number that makes the audio work.
              </p>
            </dd>
            <dt id="MM_AUDIO_RECON_DISP_FOR_RELOAD_ELD"><strong>MM_AUDIO_RECON_DISP_FOR_RELOAD_ELD</strong></dt>
            <dd>
              <p>
                Use xrandr to reconnect display in hope it will trigger reload of ELD data. Valid values are empty string
                or integer value, with empty string as default'. Empty string disables this function.
              </p>
              <p>
                Since ver.1.0.25 ALSA has capability of on-line detecting audio capabilites of devices connected to DVI/HDMI/DisplayPort. 
                By this there is possibility that MiniMyth2 will resume (and probe audio capabilities) ealier than TV/Receiver
                connected display is able to answer. This will result with wrong (or lack of at all) detected AUDIO capabilites.
                This function allows to ask to reload ELD data by shortly disconnecting and connecting again display. As some
                TV/Receivers needs some time to become responsive on EDID channel - this function allows to declare delay (in sec.)
                when display is connected again. Such delay can give TV/Receiver time to become reponsive again on EDID channel.
              </p>
            </dd>
            <dt id="MM_AUDIO_FETCH_ASOUND_CONF"><strong>MM_AUDIO_FETCH_ASOUND_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                'asound.conf' file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes', 'no' and empty', with empty the default.
              </p>
            </dd>
            <dt id="MM_AUDIO_FETCH_ASOUND_STATE"><strong>MM_AUDIO_FETCH_ASOUND_STATE</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                'asound.state' file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes', 'no' and empty', with empty the default. If set to 'yes', MiniMyth2 will
                skip unmuting all inputs/outputs by amixer and restore all amixer settings from this file.
              </p>
            </dd>
            <dt id="MM_AUDIO_IN_CARD_NUMBER"><strong>MM_AUDIO_IN_CARD_NUMBER</strong></dt>
            <dd>
              <p>
                Set audio card number for capture device. This is usefull when system has more that one audio card and
                audio output is on different card that audio input. If this variable is not set, audio input card is thesame
                like audio output card (autodetected by udev or set by MM_AUDIO_CARD_NUMBER).
                Valid values are: empty and any non-negative integer, with empty the default'.
              </p>
            </dd>
            <dt id="MM_AUDIO_DEVICE_UCM_PROFILE"><strong>MM_AUDIO_DEVICE_UCM_PROFILE</strong></dt>
            <dd>
              <p>
                Set audio card UCM profile for systems using ASoC supported by ALSA use-case manager
                <a href="https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2">UCM2</a>.
                This varialble represents card parameter used when
                <a href="https://www.systutorials.com/docs/linux/man/1-alsaucm/">alsaucm</a> utility is called to
                configure audio.
                Valid values are: empty and string, with empty the default'.
              </p>
            </dd>
            <dt id="MM_AUDIO_DEVICE_UCM_COMMAND"><strong>MM_AUDIO_DEVICE_UCM_COMMAND</strong></dt>
            <dd>
              <p>
                Set audio UCM command string to switch to desired use-case profile for systems using ASoC supported by
                ALSA use-case manager <a href="https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2">UCM2</a>.
                This variable represents command string used after card parameter when
                <a href="https://www.systutorials.com/docs/linux/man/1-alsaucm/">alsaucm</a> utility is called to
                configure audio.
                Valid values are: empty and string, with empty the default'.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_VIDEO" class="section">
          <div class="heading">Configuration variables for: video</div>
          <ul>
            <li><a href="#MM_VIDEO-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_VIDEO_PLAYBACK_PROFILE">MM_VIDEO_PLAYBACK_PROFILE</a></li>
          </ul>
          <dl>
            <dt id="MM_VIDEO-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Video related configuration variables. In MiniMyth2, Myth video proviles can work in 2 basic
                modes: 1\selected by user or 2\forced by administrator. Selection of this mode is dependent on
                <a href="#MM_VIDEO_PLAYBACK_PROFILE">MM_VIDEO_PLAYBACK_PROFILE</a> variable. If forced by
                administrator mode is selected, MiniMyth2 will use user predefined profile.
              </p>
            </dd>
            <dt id="MM_VIDEO_PLAYBACK_PROFILE"><strong>MM_VIDEO_PLAYBACK_PROFILE</strong></dt>
            <dd>
              <p>
                Set the name of the MythTV video playback profile to use.
                Valid values are: empty, 'auto', 'userdefined' or any video playback profile with name 'string', 
                with empty as the default.
              </p>
              <p>
                If this variable isn't defined, empty value will be assumed.
              </p>
              <p>
                If value is empty or undefined, MiniMyth2 at first, initial run will set MythTV video playback profile
                to build-in profile best matching detected HW.
                Following selection is implemented:
                <ul>
                  <li>Intel VAAPI capable graphics card: 'VAAPI Normal' MythTV video playback profile</li>
                  <li>Nvidia VDPAU capable graphics card: VDPAU Normal' MythTV video playback profile</li>
                  <li>Radeon VDPAU capable graphics card: 'VDPAU Normal' MythTV video playback profile</li>
                  <li>VMware virtualized graphics card: 'Slim' MythTV video playback profile</li>
                  <li>Other/unknown graphics cards: 'Normal' MythTV video playback profile</li>
                </ul>
                Also theme painter will be seto to 'auto'.
                At next runs, MiniMyth2 will not anymore touching MythTV video playback profile preserving 
                any user changes/modifications in  MythTV video playback profile.
                NOTE: First/initial run detection is based on checking JUMP MAINMENU jumppoint.
                If this jumppoint is set to 'Alt+H' - MiniMyth2 assumes it is NOT first run.
              </p>
              <p>
                If the value is 'auto', then MiniMyth2 - after HW autodetection - MiniMyth2 will pick the 'best'
                video playback profile and set it as current video playback profile. Following mapping
                is implemented:
                <ul>
                  <li>Intel VAAPI capable graphics card: MM_VIDEO_PLAYBACK_PROFILE='VAAPI Normal'</li>
                  <li>Nvidia VDPAU capable graphics card: MM_VIDEO_PLAYBACK_PROFILE='VDPAU Normal'</li>
                  <li>Radeon VDPAU capable graphics card: MM_VIDEO_PLAYBACK_PROFILE='VDPAU Normal'</li>
                  <li>VMware virtualized graphics card: MM_VIDEO_PLAYBACK_PROFILE='Slim'</li>
                  <li>Other graphics cards: MM_VIDEO_PLAYBACK_PROFILE='Normal'</li>
                </ul>
                Also theme painter will be seto to 'auto'.
              </p>
              <p>
                If 'userdefined' is value is selected, MiniMyth2 will use current video profile selected
                by user in Myth Settings GUI.
              </p>
              <p>
                If 'string' value is selected, MiniMyth2 will override user selecttion in Myth GUI and will
                select profile with name equal to 'string'.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_X" class="section">
          <div class="heading">Configuration variables for: X</div>
          <ul>
            <li><a href="#MM_X-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_X_ENABLED">MM_X_ENABLED</a></li>
            <li><a href="#MM_X_HW_TYPE">MM_X_HW_TYPE</a></li>
            <li><a href="#MM_RESTART_ON_SLEEP">MM_RESTART_ON_SLEEP</a></li>
            <li><a href="#MM_X_WM_ENABLED">MM_X_WM_ENABLED</a></li>
            <li><a href="#MM_X_VNC_ENABLED">MM_X_VNC_ENABLED</a></li>
            <li><a href="#MM_X_SCREENSAVER">MM_X_SCREENSAVER</a></li>
            <li><a href="#MM_X_SCREENSAVER_TIMEOUT">MM_X_SCREENSAVER_TIMEOUT</a></li>
            <li><a href="#MM_X_SCREENSAVER_HACK">MM_X_SCREENSAVER_HACK</a></li>
            <li><a href="#MM_X_MYTH_PROGRAM">MM_X_MYTH_PROGRAM</a></li>
            <li><a href="#MM_X_FETCH_XINITRC">MM_X_FETCH_XINITRC</a></li>
            <li><a href="#MM_X_FETCH_XMODMAPRC">MM_X_FETCH_XMODMAPRC</a></li>
            <li><a href="#MM_X_FETCH_XORG_CONF">MM_X_FETCH_XORG_CONF</a></li>
            <li><a href="#MM_X_MYTH_RSS_FOR_X_RESTART">MM_X_MYTH_RSS_FOR_X_RESTART</a></li>
            <li><a href="#MM_X_WATCHDOG_MYTH_PROC">MM_X_WATCHDOG_MYTH_PROC</a></li>
            <li><a href="#MM_X_VDPAU_ENV">MM_X_VDPAU_ENV</a></li>
            <li><a href="#MM_MYTHFRONTEND_CMDLINE">MM_MYTHFRONTEND_CMDLINE</a></li>
          </ul>
          <dl>
            <dt id="MM_X-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                The X configuration variables can be divided into five groups: application, output, display, hack and fetch.
                The X application configuration variables configure which X applications are to be enabled.
                The X output configuration variables configure which video outputs are to be enabled.
                The X display configuration variables configure the parameters of the X display.
                The X hack configuration variables cause different X related hacks to be applied.
                The X fetch configuration variables cause different X related files to be fetched.
              </p>
            </dd>
            <dt id="MM_X_ENABLED"><strong>MM_X_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable the
                <a href="http://en.wikipedia.org/wiki/X_Window_System">X Window System</a>.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                MiniMyth2 requires the X Window System in order to run MythTV and other X application.
                Normally, there should be no reason to use 'MM_X_ENABLED' to disable the X Window System.
                However, when you are deguggin MiniMyth2, it can sometimes be useful to disable the X Window System.
              </p>
              <p>
                MiniMyth2 uses the
                <a href="http://xorg.freedesktop.org/wiki/">Xorg</a>
                X Window System.
              </p>
            </dd>
            <dt id="MM_X_HW_TYPE"><strong>MM_X_HW_TYPE</strong></dt>
            <dd>
              <p>
                Indicate the X graphics hardware type to use.
                Valid values are:
                <ul>
                  <li>intel</li>
                  <li>intel_vaapi</li>
                  <li>nvidia</li>
                  <li>nvidia_vdpau</li>
                  <li>nvidia_legacy</li>
                  <li>nvidia_lagacy_vdpau</li>
                  <li>radeon</li>
                  <li>radeon_vdpau</li>
                  <li>vmware</li>
                  <li>armsoc</li>
                  <li>meson</li>
                  <li>rockchip</li>
                  <li>sun4i</li>
                  <li>vc4</li>
                </ul>
              </p>
              <p>
                In normal conditions this variable should not be needed.
                If your hardware's video driver is not detected, then this variable allows You to force detection to given 
                hardware category. In such case please ask us to add Your hardware to suported hardware list. Please go to 
                <a href="http://MiniMyth2.freeforums.org">and let us know about</a>
                the output of 'lspci&nbsp;-mn' as well as the correct video driver.
              </p>
            </dd>
            <dt id="MM_RESTART_ON_SLEEP"><strong>MM_RESTART_ON_SLEEP</strong></dt>
            <dd>
              <p>
                Indicate what to do during sleep-resume cycle.
                Valid values are:
                <ul>
                  <li>none</li>
                  <li>mythfrontend</li>
                  <li>mythstandby</li>
                  <li>xorg</li>
                  <li>xorg-after-resume</li>
                </ul>
                with default value set to 'none'
              </p>
              <p>
                With some X video drivers on some hardware, X hangs when returning from sleep.
                If you are using sleep and X hangs when returning from sleep,
                then setting this variable to 'xorg' or 'xorg-after-resume' may help.
                Selecting 'xorg' will cause stopping X before entering sleep state and restarting
                X after resume. Selecting 'xorg-after-resume' will restart (stop and start again) X 
                after resume. 'xorg-after-resume' might be usueful when video drivers have bug causing i.e
                black screen after when X are asked to start just after resume.
                MythTV is not yet designed to properly handle sleep-resume.
                Setting this value to 'mythfrontend' helps to resolve i.e. issue
                of not autorefreshing of schedules on EPG when myth was sleep longer than
                few hours. Setting to 'mythstandby' will put mythfrontend into standby before sleep and 
                waking mythfrontend from standby after wokeup from sleep.
                Setting to 'none' disables this function.
              </p>
              <p>
                Before trying this variable, try
                <a href="#MM_ACPI_VIDEO_FLAGS">MM_ACPI_VIDEO_FLAGS</a>.
              </p>
            </dd>
            <dt id="MM_X_WM_ENABLED"><strong>MM_X_WM_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable the
                <a href="http://en.wikipedia.org/wiki/Window_manager">X window manager</a>.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                MythTV and other X applications may not work correctly without an X window manager.
                For example, the MythBrowser and MythGame plugins will not work correctly without an X window manager.
                In addition, keyboard navigation will not work correctly without an X window manager.
                Therefore, you should not disable the X window manager.
              </p>
              <p>
                MiniMyth2 uses the
                <a href="http://www.nongnu.org/ratpoison/">ratpoison</a>
                X window manager.
              </p>
            </dd>
            <dt id="MM_X_VNC_ENABLED"><strong>MM_X_VNC_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable the X
                <a href="http://en.wikipedia.org/wiki/VNC">Virtual Network Computing (VNC)</a>
                server.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                VNC can be used to attach to either real or virtual X Window displays.
                A real X display is an X display that is attached to a console (e.g. your television).
                That is, the X display seen on the console and seen by the VNC client are the same X session.
                A virtual X display is an X display that is not attached to a console.
                That is, the X display seen on the console and seen by the VNC client are different X sessions.
              </p>
              <p>
                A VNC server can enable attachment to either real or virtual X window displays but not both.
                The reason for including a VNC server in MiniMyth2 is to enable keyboard entry of MythTV data
                without requiring a keyboard be connected to the MiniMyth2 MythTV frontend.
                Therefore, the MiniMyth2 VNC server serves the real X display and not virtual X displays.
              </p>
              <p>
                When security is enabled (<a href="#MM_SECURITY_ENABLED">MM_SECURITY_ENABLED</a>='yes'),
                the VNC server listens on and allows connections from localhost (127.0.0.1) only.
                To connect to the VNC server,
                you will need to enable the SSH server (<a href="#MM_SSH_SERVER">MM_SSH_SERVER</a>) and
                <a href="http://www.karlrunge.com/x11vnc/#tunnelling">tunnel VNC over SSH</a>.
              </p>
              <p>
                When security is disabled (<a href="#MM_SECURITY_ENABLED">MM_SECURITY_ENABLED</a>='no'),
                the VNC server listens on and allows connections from all IP addresses.
              </p>
              <p>
                MiniMyth2 uses the
                <a href="http://www.karlrunge.com/x11vnc/">x11vnc</a>
                VNC server.
              </p>
            </dd>
            <dt id="MM_X_SCREENSAVER"><strong>MM_X_SCREENSAVER</strong></dt>
            <dd>
              <p>
                Set the X
                <a href="http://en.wikipedia.org/wiki/Screensaver">screensaver</a>
                to use.
                Valid values are 'none', 'xorg' and 'xscreensaver', with 'none' the default.
              </p>
              <p>
                If an X screensaver is selected, then MiniMyth2 will blank the screen after a short period of inactivity (2 minutes).
                This can be useful when MiniMyth2 is connected to a display that is subject to
                <a href="http://en.wikipedia.org/wiki/Phosphor_burn-in">burn-in</a>.
              </p>
              <p>
                MiniMyth2 supports both the xorg screensaver (MM_X_SCREENSAVER='xorg') and XScreenSaver screensaver (MM_X_SCREENSAVER='xscreensaver'),
                because neither screensaver works with all displays.
              </p>
            </dd>
            <dt id="MM_X_SCREENSAVER_TIMEOUT"><strong>MM_X_SCREENSAVER_TIMEOUT</strong></dt>
            <dd>
              <p>
                Set the screensaver timeout in minutes.
                Valid values are positive integers, with '10' the default.
              </p>
            </dd>
            <dt id="MM_X_SCREENSAVER_HACK"><strong>MM_X_SCREENSAVER_HACK</strong></dt>
            <dd>
              <p>
                Set the XScreenSaver hack to use when using XScreenSaver as the screensaver.
                Valid values are 'sleep', 'blank' and 'glslideshow', with 'sleep' the default.
              </p>
              <p>
                The 'sleep' hack is special.
                It sets the actual XScreenSaver hack to 'blank' and
                puts the MiniMyth2 frontend to sleep when XScreenSaver activates.
              </p>
              <p>
                The 'glslideshow' hack randomly displays JPEG (*.jpg) images found in the image gallery directory
                ('<a href="#MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT">MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT</a>').
                This image gallery directory is mounted with ('<a href="#MM_MEDIA_SCREENSAVER_GALLERY_URL">MM_MEDIA_SCREENSAVER_GALLERY_URL</a>').
              </p>
            </dd>
            <dt id="MM_X_MYTH_PROGRAM"><strong>MM_X_MYTH_PROGRAM</strong></dt>
            <dd>
              <p>
                Set the myth program to run.
                Valid values are 'mythfrontend' and 'mythwelcome', with 'mythfrontend' the default.
              </p>
            </dd>
          </dl>
          <p>
            The X fetch configuration variables are:
          </p>
          <dl>
            <dt id="MM_X_FETCH_XINITRC"><strong>MM_X_FETCH_XINITRC</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#xinitrc">xinitrc</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
          </dl>
          <dl>
            <dt id="MM_X_FETCH_XORG_CONF"><strong>MM_X_FETCH_XORG_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#xorg_conf">xorg.conf</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
          </dl>
          <dl>
            <dt id="MM_X_MYTH_RSS_FOR_X_RESTART"><strong>MM_X_MYTH_RSS_FOR_X_RESTART</strong></dt>
            <dd>
              <p>
                Indicate whether or not MiniMyth2 should monitor current RAM usage
                (in percentage of total RAM). This variable is an treshold for forcing
                reload of mythfrontend process when RAM usage exceeds this treshold.
                Valid values are '0-100'. If this variable in not present - RAM usage
                monitoring function is disabled. Is tris setting is empty, feature is 
                enabled and RAM usage is set to 60%.
              </p>
            </dd>
          </dl>
          <dl>
            <dt id="MM_X_WATCHDOG_MYTH_PROC"><strong>MM_X_WATCHDOG_MYTH_PROC</strong></dt>
            <dd>
              <p>
                Indicate whether or not MiniMyth2 should watchdog is mythfrontend process
                still runing. If no runing mythfrontend process is detected - MiniMyth2
                will force reload of X-server.
                Valid values are 'yes' and 'no' with 'no' te default.
              </p>
            </dd>
          </dl>
          <dl>
            <dt id="MM_MYTHFRONTEND_CMDLINE"><strong>MM_MYTHFRONTEND_CMDLINE</strong></dt>
            <dd>
              <p>
                If set to non-empty it will be used as added mythfrontend command-line parameters 
                passed to call of /usr/bin/mythfrontend > /var/log/mythfrontend. 
                So seting MM_MYTHFRONTEND_CMDLINE="-v all" will cause
                launch "/usr/bin/mythfrontend -v all > /var/log/mythfrontend"
                Valid values are 'string' and empty.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_FONT" class="section">
          <p>
          </p>
          <div class="heading">Configuration variables for: fonts</div>
          <ul>
            <li><a href="#MM_FONT-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_FONT_FILE_TTF_ADD">MM_FONT_FILE_TTF_ADD</a></li>
            <li><a href="#MM_FONT_FILE_TTF_DELETE">MM_FONT_FILE_TTF_DELETE</a></li>
          </ul>
          <dl>
            <dt id="MM_FONT-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Font related configuration variables.
              </p>
            </dd>
            <dt id="MM_FONT_FILE_TTF_ADD"><strong>MM_FONT_FILE_TTF_ADD</strong></dt>
            <dd>
              <p>
                A list of TrueType font (TTF) files to add.
                These font files will be fetched from the frontend's MiniMyth2 read-only configuration directory.
              </p>
              <p>
                MiniMyth2 contains
                <a href="https://www.redhat.com/promo/fonts/">the Liberation font</a>,
                which provides reasonable
                <a href="http://en.wikipedia.org/wiki/Monospace_font">monospace</a>,
                <a href="http://en.wikipedia.org/wiki/Serif">serif</a>
                and
                <a href="http://en.wikipedia.org/wiki/Sans-serif">sans-serif</a>
                fonts.
                The main reason for needing to add additional fonts is that
                the Liberation font does not contain all characters.
                For instance, the Liberation font do not contain Chinese characters.
                Therefore, if you need to display Chinese characters, then you will need to add additional fonts.
              </p>
            </dd>
            <dt id="MM_FONT_FILE_TTF_DELETE"><strong>MM_FONT_FILE_TTF_DELETE</strong></dt>
            <dd>
              <p>
                A list of TrueType font (TTF) files to delete.
                These font files will be deleted from the frontend directory '/usr/lib/X11/fonts/TTF'.
                The list can include pathname expansion patterns (e.g. '*.TTF *.ttf' would match all TTF files).
              </p>
              <p>
                In general, there should be no need to delete font files.
                However, if there are fonts that you do not want use,
                then you can ensure that they will not be used by deleting them.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_MAIL" class="section">
          <p>
          </p>
          <div class="heading">Configuration variables for: Mail notifications</div>
          <ul>
            <li><a href="#MM_MAIL-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MAIL_NOTIFY_NEW_MAILS">MM_MAIL_NOTIFY_NEW_MAILS</a></li>
            <li><a href="#MM_MAIL_NOTIFY_ALL_ON_RESUME">MM_MAIL_NOTIFY_ALL_ON_RESUME</a></li>
            <li><a href="#mailnotifier_rc">mailnotifier.rc</a></li>
          </ul>
          <dl>
            <dt id="MM_MAIL-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Mail notification related configuration variables. MiniMyth2 can notify new mails arrival via OSD.
                MiniMyth2 has build in daemon which will periodically check defined in configuration file mail
                accounts. When new mail will be detected, MiniMyth2 can display To:, From: and Subject: filelds
                of each mail via OSD.
              </p>
            </dd>
            <dt id="MM_MAIL_NOTIFY_NEW_MAILS"><strong>MM_MAIL_NOTIFY_NEW_MAILS</strong></dt>
            <dd>
              <p>
                If this variable is present, it enables mail notifcations. Value of this variable
                defines time interval (in seconds) for checking new mails.
              </p>
            </dd>
            <dt id="MM_MAIL_NOTIFY_ALL_ON_RESUME"><strong>MM_MAIL_NOTIFY_ALL_ON_RESUME</strong></dt>
            <dd>
              <p>
                This variable determines wheter - after resume from sleep - MiniMyth2 should notify all
                mails or only new mails.
              </p>
            </dd>
            <dt id="mailnotifier_rc"><strong>mailnotifier.rc</strong></dt>
            <dd>
              <p>
                This is configuration file for mail accounts to be checked by mail notify function.
                For details pls refer to <a href="document-configure.html#misc">mailnotifier.rc</a> section in
                miscellaneous configuration files document.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_MYTH" class="section">
          <p>
          </p>
          <div class="heading">Configuration variables for: MythTV</div>
          <ul>
            <li><a href="#MM_MYTH-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MYTHTV_HOME_URL">MM_MYTHTV_HOME_URL</a></li>
            <li><a href="#MM_MYTHTV_HOME_RAMDISK">MM_MYTHTV_HOME_RAMDISK</a></li>
            <li><a href="#MM_REMOTECACHE_URL">MM_REMOTECACHE_URL</a></li>
            <li><a href="#MM_AIRPLAY_ENABLED">MM_AIRPLAY_ENABLED</a></li>
            <li><a href="#MM_WUNDERGROUND_KEY">MM_WUNDERGROUND_KEY</a></li>
            <li><a href="#MM_LOAD_BROWSER_COOKIES">MM_LOAD_BROWSER_COOKIES</a></li>
            <li><a href="#MM_NETFLIX_ENABLED">MM_NETFLIX_ENABLED</a></li>
          </ul>
          <dl>
            <dt id="MM_MYTH-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                MythTV related configuration variables.
              </p>
            </dd>
            <dt id="MM_MYTHTV_HOME_URL"><strong>MM_MYTHTV_HOME_URL</strong></dt>
            <dd>
              <p>
                If this variable is set, it enables mapping MiniMyth2 home dir on remote server.
                If it is set to "auto", MiniMyth2 assumes there is one main NFS share used as MiniMyth2 boot dir.
                In such case MiniMyth2 will assume MiniMyth2 home dir content is located in
                "MM_MINIMYTH_BOOT_DIR"/conf-rw/"host_name"/minimyth_home/". NOTE: MM_MINIMYTH_BOOT_DIR is guessed from
                boot process - but if MiniMyth2 is booted from other protocol than NFS, MM_MINIMYTH_BOOT_DIR should
                be setup in minimyth.conf file (like i.e. MM_MINIMYTH_BOOT_URL="nfs://192.168.1.254/tftpboot/PXEclient)".
                Generally, 'auto' is suitable for setups where MiniMyth2 want's to use only one NFS share for: conf-ro, conf-rw,
                MiniMyth2 home, and extras (if MM_EXTRAS_URL is set to 'global') instead of mounting separate NFS share for each dir.
                MiniMyth2 will also autoinitialize home dir - if remote share hasn't proper content. At every boot
                MiniMyth2 is checking presence of ./mythtv/mysql.txt file. If on remote share this file is present - MiniMyth2
                will assume home dir is present and properly initialized. If this file isn't present, MiniMyth2 will:
                1. copy all files from local /home/minimyth/* to remote home dir
                2. delete local /home/minimyth*
                3. mount remote home dir to /home/minimyth
              </p>
            </dd>
            <dt id="MM_MYTHTV_HOME_RAMDISK"><strong>MM_MYTHTV_HOME_RAMDISK</strong></dt>
            <dd>
              <p>
                If this variable is present, and MM_HOME_URL is not set, MiniMyth2 will create tmpfs based RAM
                disk for mythtv home dir. If it is set to 'none' - RAM disk will be not created. Default value is '256'.
              </p>
            </dd>
            <dt id="MM_REMOTECACHE_URL"><strong>MM_REMOTECACHE_URL</strong></dt>
            <dd>
              <p>
                If this variable is present, and MM_HOME_URL is not set, it enables mapping mythtv remotecache dir
                to URL share. If set to 'auto' then MiniMyth2 will map mythtv's remotecache to 
                "MM_MINIMYTH_BOOT_DIR"/conf-rw/"host_name"/remotecache/". NOTE: MM_MINIMYTH_BOOT_DIR is guessed from boot
                process - but if MiniMyth2 is booted from other protocols than NFS, MM_MINIMYTH_BOOT_DIR should
                be setup in minimyth.conf file (like i.e. MM_MINIMYTH_BOOT_URL="nfs://192.168.1.254/tftpboot/PXEclient").
                If set to 'none' - no remotecache mapping will be done. Default value is 'none'.
              </p>
            </dd>
            <dt id="MM_AIRPLAY_ENABLED"><strong>MM_AIRPLAY_ENABLED</strong></dt>
            <dd>
              <p>
                If this variable is set to YES, it enables airplay support on mythfrontend. If this functionality is 
                enabled, MiniMyth2 will download RAOPkey.rsa file
                from conf-ro directory and enable AirPlay functionality on Mythfrontend. Valid values are 
                'yes', 'no' and empty. Empty value means 'no'.
              </p>
            </dd>
            <dt id="MM_WUNDERGROUND_KEY"><strong>MM_WUNDERGROUND_KEY</strong></dt>
            <dd>
              <p>
                If this variable is set to YES, it enables downloading wunderground.key from MiniMyth2 conf-ro location.
                This file is needed as MythTV 0.26 uses key signed API to access <a href="http://www.wunderground.com">wunderground.com</a>
                site. Signing for key requires registration on <a href="http://www.wunderground.com/weather/api">API registration page</a>
                Valid values are 'yes', 'no' and empty. Empty value means 'no'.
              </p>
            </dd>
            <dt id="MM_LOAD_BROWSER_COOKIES"><strong>MM_LOAD_BROWSER_COOKIES</strong></dt>
            <dd>
              <p>
                If this variable is set to YES, it enables downloading MythBrowser cookiejar.txt file from MiniMyth2 conf-rw location.
                This file has saved WEB cookies from WEB pages visited by MythBrowser. User can save current cookies by
                using "Save Cookies" command located in Myth-At-Home maintain menu.
                Valid values are 'yes', 'no' and empty. Empty variable means 'no'.
              </p>
            </dd>
            <dt id="MM_NETFLIX_ENABLED"><strong>MM_NETFLIX_ENABLED</strong></dt>
            <dd>
              <p>
                If this variable is set to 'yes', it enables Netflix option in MythTV themes and enables download
                archived in conf-rw google-chrome state archive. User can save current google-chrome state by
                using "Save Cookies" command located in maintain menu.
                Valid values are 'yes', 'no' and empty. Empty variable means 'no'.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_MASTER" class="section">
          <div class="heading">Configuration variables for: Myth master backend communication</div>
          <ul>
            <li><a href="#MM_MASTER-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MASTER_SERVER">MM_MASTER_SERVER</a></li>
            <li><a href="#MM_MASTER_DBUSERNAME">MM_MASTER_DBUSERNAME</a></li>
            <li><a href="#MM_MASTER_DBPASSWORD">MM_MASTER_DBPASSWORD</a></li>
            <li><a href="#MM_MASTER_DBNAME">MM_MASTER_DBNAME</a></li>
            <li><a href="#MM_MASTER_WOL_ENABLED">MM_MASTER_WOL_ENABLED</a></li>
            <li><a href="#MM_MASTER_WOL_MAC">MM_MASTER_WOL_MAC</a></li>
            <li><a href="#MM_MASTER_WOLSQLRECONNECTWAITTIME">MM_MASTER_WOLSQLRECONNECTWAITTIME</a></li>
            <li><a href="#MM_MASTER_WOLSQLCONNECTRETRY">MM_MASTER_WOLSQLCONNECTRETRY</a></li>
            <li><a href="#MM_MASTER_WOLSQLCOMMAND">MM_MASTER_WOLSQLCOMMAND</a></li>
          </ul>
          <dl>
            <dt id="MM_MASTER-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Myth master backend communication related configuration variables.
              </p>
            </dd>
            <dt id="MM_MASTER_SERVER"><strong>MM_MASTER_SERVER</strong></dt>
            <dd>
              <p>
                Set the DNS name or IP address of the MythTV master backend (mysql.txt:DBHostName).
                If not specified, it defaults to the TFTP server's IP address.
              </p>
            </dd>
            <dt id="MM_MASTER_DBUSERNAME"><strong>MM_MASTER_DBUSERNAME</strong></dt>
            <dd>
              <p>
                Set the MythTV master backend database username (mysql.txt:DBUserName).
                Valid values are any string, with 'mythtv' the default.
              </p>
            </dd>
            <dt id="MM_MASTER_DBPASSWORD"><strong>MM_MASTER_DBPASSWORD</strong></dt>
            <dd>
              <p>
                Set the MythTV master backend database password (mysql.txt:DBPassword).
                Valid values are any string, with 'mythtv' the default.
              </p>
            </dd>
            <dt id="MM_MASTER_DBNAME"><strong>MM_MASTER_DBNAME</strong></dt>
            <dd>
              <p>
                Set the MythTV master backend database name (mysql.txt:DBName).
                Valid values are any string, with 'mythconverg' the default.
              </p>
            </dd>
            <dt id="MM_MASTER_WOL_ENABLED"><strong>MM_MASTER_WOL_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable wake-on-lan.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
            <dt id="MM_MASTER_WOL_MAC"><strong>MM_MASTER_WOL_MAC</strong></dt>
            <dd>
              <p>
                Set the MAC address of the MythTV master backend.
                The default is '00:00:00:00:00:00'.
              </p>
            </dd>
            <dt id="MM_MASTER_WOLSQLRECONNECTWAITTIME"><strong>MM_MASTER_WOLSQLRECONNECTWAITTIME</strong></dt>
            <dd>
              <p>
                Set the MythTV master backend WOL database reconnect wait time in seconds (WOLSqlReconnectWaitTime).
                Valid values are any positive integer, with '15' the default.
              </p>
            </dd>
            <dt id="MM_MASTER_WOLSQLCONNECTRETRY"><strong>MM_MASTER_WOLSQLCONNECTRETRY</strong></dt>
            <dd>
              <p>
                Set the MythTV master backend WOL database connection retries (WOLSqlConnectRetry).
                Valid values are any positive integer, with '20' the default.
              </p>
            </dd>
            <dt id="MM_MASTER_WOLSQLCOMMAND"><strong>MM_MASTER_WOLSQLCOMMAND</strong></dt>
            <dd>
              <p>
                Set the MythTV master backend WOL command.
                The default is 'wakelan&nbsp;-b&nbsp;{broadcast}&nbsp;-m&nbsp;{mac}',
                where {broadcast} is the subnet broadcast address,
                and {mac} is
                '<a href="#MM_MASTER_WOL_MAC">MM_MASTER_WOL_MAC</a>'.
              </p>
            </dd>
            <dt id="MM_MASTER_WOL_ADDITIONAL_DELAY"><strong>MM_MASTER_WOL_ADDITIONAL_DELAY</strong></dt>
            <dd>
              Set the additional delay in seconds to wait for the MythTV master backend to wake after connecting to the database.
              Valid valies are any non-negative integer, with '0' the default.
            </dd>
          </dl>
        </div>
        <div id="MM_PLUGIN" class="section">
          <div class="heading">Configuration variables for: Myth plugins</div>
          <ul>
            <li><a href="#MM_PLUGIN-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_PLUGIN_OPTICAL_DISK_ENABLED">MM_PLUGIN_OPTICAL_DISK_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_BROWSER_ENABLED">MM_PLUGIN_BROWSER_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_GALLERY_ENABLED">MM_PLUGIN_GALLERY_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_GAME_ENABLED">MM_PLUGIN_GAME_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_MUSIC_ENABLED">MM_PLUGIN_MUSIC_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_NEWS_ENABLED">MM_PLUGIN_NEWS_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_WEATHER_ENABLED">MM_PLUGIN_WEATHER_ENABLED</a></li>
            <li><a href="#MM_PLUGIN_ZONEMINDER_ENABLED">MM_PLUGIN_ZONEMINDER_ENABLED</a></li>
          </ul>
          <dl>
            <dt id="MM_PLUGIN-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Myth plugins related configuration variables.
              </p>
            </dd>
            <dt id="MM_PLUGIN_OPTICAL_DISK_ENABLED"><strong>MM_PLUGIN_OPTICAL_DISK_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythTV support for 'Optical Disks' menu.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                If you are disabling all plugins under the  'Optical Disks' menu,
                or you do not have an optical disk,
                then disabling the 'Information Center' menu can reduce menu clutter.
              </p>
            </dd>
            <dt id="MM_PLUGIN_BROWSER_ENABLED"><strong>MM_PLUGIN_BROWSER_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythBrowser.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
            </dd>
            <dt id="MM_PLUGIN_GALLERY_ENABLED"><strong>MM_PLUGIN_GALLERY_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythGallery.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
            </dd>
            <dt id="MM_PLUGIN_GAME_ENABLED"><strong>MM_PLUGIN_GAME_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythGame.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
            </dd>
            <dt id="MM_PLUGIN_MUSIC_ENABLED"><strong>MM_PLUGIN_MUSIC_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythMusic.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
            </dd>
            <dt id="MM_PLUGIN_NEWS_ENABLED"><strong>MM_PLUGIN_NEWS_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythNews.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
            </dd>
            <dt id="MM_PLUGIN_WEATHER_ENABLED"><strong>MM_PLUGIN_WEATHER_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythWeather.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
            </dd>
            <dt id="MM_PLUGIN_ZONEMINDER_ENABLED"><strong>MM_PLUGIN_ZONEMINDER_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable MythZoneMinder.
                Valid values are 'yes' and 'no',
                with 'yes' the default when the plugin is present and 'no' the default when the plugin is not present.
              </p>
              <p>
                The MythZoneMinder plugin was added after MythTV release 0.20.x.
                Therefore, this setting does not apply to MythTV release 0.20.x.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_EXTRAS" class="section">
          <div class="heading">Configuration variables for: Extras directory</div>
          <ul>
            <li><a href="#MM_EXTRAS-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_EXTRAS_URL">MM_EXTRAS_URL</a></li>
          </ul>
          <dl>
            <dt id="MM_EXTRAS-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                You can extend MiniMyth2 by adding files under /usr/local.
              </p>
              <p>
                The
                <a href="http://en.wikipedia.org/wiki/Uniform_Resource_Locator">Uniform Resource Locators (URLs)</a>
                in this section must have the following form:
              </p>
              <p>
                {protocol}://{username}:{password}@{server}/{path}?{options}
              </p>
              <p>
                where {options} are additional mount options (-o).
                For example:
              </p>
              <p>
                nfs://server.home/home/public/music<br/>
                cifs://user:pass@server.home/music?domain=home<br/>
                confrw:G.A.N.T..1024.768.sfs<br/>
              </p>
              <p>
                The valid protocol values are: 'nfs', 'cifs', 'http', 'tftp', 'confro', 'confrw', 'dist', 'hunt' and 'file'.
                For 'nfs' and 'cifs' the URL points to a remote directory.
                For 'http', 'tftp', 'confro', 'confrw', 'dist' and 'hunt', the URL points to a remote file.
                For 'file', the URL points to a local directory or file.
                A directory will be mounted at the mount point.
                A file, which can be a squashfs image (*.sfs.), cramfs image (*.cmg) or a tarball file (*.tar.bz2)
                will be retrieved and mounted at (for *.sfs and *.cmg files) or retrieved at expanded into (for *.tar.bz2 files) the mount point.
                The 'confro', 'confrw', 'dist' and 'hunt' are special MiniMyth2 specific URLs.
                A 'dist' URL causes MiniMyth2 to look for the file in the MiniMyth2 distribution directory
                (the directory with the MiniMyth2 root file system squashfs image).
                A 'confro' URL causes MiniMyth2 to look for the file in the MiniMyth2 read-only configuration directory.
                A 'confrw' URL causes MiniMyth2 to look for the file in the MiniMyth2 read-write configuration directory.
                A 'hunt' URL causes MiniMyth2 to look for the file first in the MiniMyth2 distribution directory and
                second in the MiniMyth2 read-only configuration directory.
              </p>
            </dd>
            <dt id="MM_EXTRAS_URL"><strong>MM_EXTRAS_URL</strong></dt>
            <dd>
              <p>
                Set the location of the extras directory that will be mounted as '/usr/local'.
                Valid values are a URL, 'none' 'auto' and 'global', with 'none' being the default.
              </p>
              <p>
                If the value is 'none',
                then nothing will be mounted as '/usr/local'.
              </p>
              <p>
                If the value is 'auto',
                MiniMyth2 will assume there is NFS share with base boot dir. MiniMyth2 will assume extras content is in:<br/><br/>
                {base_boot_dir}/extras/{host_name}/<br/><br/>Minimyth instead of mounting separate share
                for extras content, will symlink above subdir to /usr/local and issue ldconfig
              </p>
              <p>
                If the value is 'global',
                MiniMyth2 will assume there is NFS share with base boot dir. MiniMyth2 will assume extras content is in:<br/><br/>
                {base_boot_dir}/extras/<br/><br/>MiniMyth2 instead of mounting separate share
                for extras content, will symlink above subdir to /usr/local and issue ldconfig
              </p>
            </dd>
          </dl>
          <p>
            Alternatively, you can mount the extras directory by adding the appropriate commands to the 'minimyth.script' package.
          </p>
        </div>
        <div id="MM_FLASH" class="section">
          <div class="heading">Configuration variables for: Adobe Flash Player</div>
          <ul>
            <li><a href="#MM_FLASH-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_FLASH_URL">MM_FLASH_URL</a></li>
          </ul>
          <dl>
            <dt id="MM_FLASH-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                You can extend MiniMyth2 by adding
                <a href="http://www.adobe.com/products/flashplayer/">Adobe Flash Player</a>
                for use in MythBrowser.
              </p>
              <p>
                The URLs in this section must have the form described in the
                <a href="#MM_EXTRAS">Extras directory ...</a>
                section.
              </p>
            </dd>
            <dt id="MM_FLASH_URL"><strong>MM_FLASH_URL</strong></dt>
            <dd>
              <p>
                Set the location of the Adobe Flash Player shared library that will be installed at
                '/usr/lib/browser/plugins/libflashplayer.so'.
                Valid values are a URL, 'none' and 'auto', with 'none' being the default.
              </p>
              <p>
                If the value is 'none',
                then nothing will be installed at
                '/usr/lib/browser/plugins/'.
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will assume that the file is a shared library file
                located in the MiniMyth2 read-write configuration directory and having the name 'libflashplayer.so'.
                That is, MiniMyth2 will assume MM_FLASH_URL='confrw:libflashplayer.so'.
              </p>
              <p>
                The MythTV frontend menus contain the 'Minimyth&nbsp;Tools' menu
                (under the 'Utilities&nbsp;/&nbsp;Setup' menu in a regular theme and under the main menu in a classic theme).
                The 'Minimyth&nbsp;Tools' menu contains the menu item 'Fetch&nbsp;and&nbsp;Save&nbsp;Adobe Flash Player'
                to help with creating a Adobe Flash Player shared library.
                The 'Fetch&nbsp;and&nbsp;Save&nbsp;Adobe Flash Player' menu item does the following:
              </p>
              <ol>
                <li>fetches
                  <a href="http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_10_linux.tar.gz">Adobe Flash Player</a>
                  from the Internet,</li>
                <li>creates a temporary browser plugins directory,</li>
                <li>installs the downloaded Adobe Flash Player in the temporary browser plugins directory, and</li>
                <li>saves the Adobe Flash Player shared library in the
                  <a href="document-configure.html#location">MiniMyth2 read-write configuration directory</a>.</li>
              </ol>
              <p>
                During the time that it takes MiniMyth2 to fetch and save the Adobe Flash Player shared library,
                MiniMyth2 will display a terminal window with status information.
              </p>
              <p>
                For the newly downloaded Adobe Flash Player to take effect, you must reboot your MiniMyth2 frontend.
              </p>
              <p>
                The MythBrowser did not support NPAPI plugins until after release 0.21.x.
                Therefore, this setting does not apply to MythTV until after release 0.21.x.
              </p>
              <p>
                The Adobe Flash Player shared library only supports 32-bit.
                Therefore, this setting does not apply to non-32-bit builds.
              </p>
            </dd>
          </dl>
          <p>
            Alternatively, copy the Adobe Flash Player shared library to the browser plugin directory by adding the appropriate commands to the 'minimyth.script' package.
          </p>
        </div>
        <div id="MM_THEME" class="section">
          <div class="heading">Configuration variables for: themes</div>
          <ul>
            <li><a href="#MM_THEME-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_THEME_NAME">MM_THEME_NAME</a></li>
            <li><a href="#MM_THEMEMENU_NAME">MM_THEMEMENU_NAME</a></li>
            <li><a href="#MM_THEME_URL">MM_THEME_URL</a></li>
            <li><a href="#MM_THEMEMENU_URL">MM_THEMEMENU_URL</a></li>
            <li><a href="#MM_THEMECACHE_URL">MM_THEMECACHE_URL</a></li>
            <li><a href="#MM_THEME_FILE_MENU_ADD">MM_THEME_FILE_MENU_ADD</a></li>
          </ul>
          <dl>
            <dt id="MM_THEME-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                MythTV themes are large and numerous.
                Rather than burden the MiniMyth2 root file system image with this extra size,
                MiniMyth2 downloads and mounts the MythTV theme that is to be used by the frontend.
                The MiniMyth2 distribution contains several themes, which can be found in the 'themes/' directory.
                Themes that end in 'wide' are widescreen MythTV themes.
                The remaining themes are standard MythTV themes.
                In addition to choosing from the included themes, you can use your own MythTV theme.
              </p>
              <p>
                MythTV scales the MythTV theme graphics to sizes that are appropriate for your display resolution.
                If it present and up-to-date, then this cached theme is reused each time mythfrontend is starts.
                This works well on MythTV frontend's that have non-volatile storage (e.g. a hard disk drive).
                However, MiniMyth2 systems do not have non-volatile storage.
                As a result, mythfrontend regenerates the cached theme each time that MiniMyth2 is rebooted.
                In order to enable MiniMyth2 to have all the advantages of a cached theme
                without regenerating the cached theme each time MiniMyth2 is rebooted,
                MiniMyth2 can mount the themecache directory at boot time.
              </p>
              <p>
                The URLs in this section must have the form described in the
                <a href="#MM_EXTRAS">Extras directory ...</a>
                section.
              </p>
            </dd>
            <dt id="MM_THEME_NAME"><strong>MM_THEME_NAME</strong></dt>
            <dd>
              <p>
                Set the name of the MythTV theme to be used. If empty, 'Default' will be set. MiniMyth2 will
                try download theme with name 'Default'. If MiniMyth2 fails to download or will be not able
                to find theme 'Default' then MiniMyth2 will switch to build-in 'MythCenter-wide' theme.
              </p>
            </dd>
            <dt id="MM_THEMEMENU_NAME"><strong>MM_THEMEMENU_NAME</strong></dt>
            <dd>
              <p>
                Set the name of the MythTV theme Menu to be used.
              </p>
            </dd>
            <dt id="MM_THEME_URL"><strong>MM_THEME_URL</strong></dt>
            <dd>
              <p>
                Set the location of the MythTV theme that will be mounted
                in the MythTV themes directory ('/usr/share/mythtv/themes') as
                "${<a href="#MM_THEME_NAME">MM_THEME_NAME</a>}".
                Valid values are a URL, 'none' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value is 'none',
                then nothing will be mounted in the MythTV themes directory as
                "${<a href="#MM_THEME_NAME">MM_THEME_NAME</a>}".
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will assume that the MythTV theme directory is in a squashfs image file
                located in either the MiniMyth2 distribution directory or the MiniMyth2 read-only configuration directory and
                having the name "themes/${<a href="#MM_THEME_NAME">MM_THEME_NAME</a>}.sfs".
                That is, MiniMyth2 will assume
                MM_THEME_URL="hunt:themes/${<a href="#MM_THEME_NAME">MM_THEME_NAME</a>}.sfs".
                If MiniMyth2 fails to download or will be not able
                to find theme .sfs file, then MiniMyth2 will switch to build-in 'MythCenter-wide' theme.
              </p>
            </dd>
            <dt id="MM_THEMEMENU_URL"><strong>MM_THEMEMENU_URL</strong></dt>
            <dd>
              <p>
                Set the location of the MythTV theme Menu that will be mounted
                in the MythTV themes directory ('/usr/share/mythtv/themes') as
                "${<a href="#MM_THEMEMENU_NAME">MM_THEMEMENU_NAME</a>}".
                Valid values are a URL, 'none' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value is 'none',
                then nothing will be mounted in the MythTV themes directory as
                "${<a href="#MM_THEMEMENU_NAME">MM_THEMEMENU_NAME</a>}".
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will assume that the MythTV theme Menu directory is in a squashfs image file
                located in either the MiniMyth2 distribution directory or the MiniMyth2 read-only configuration directory and
                having the name "themes/${<a href="#MM_THEMEMENU_NAME">MM_THEMEMENU_NAME</a>}.sfs".
                That is, MiniMyth2 will assume
                MM_THEMEMENU_URL="hunt:themes/${<a href="#MM_THEMEMENU_NAME">MM_THEMEMENU_NAME</a>}.sfs".
              </p>
            </dd>
            <dt id="MM_THEMECACHE_URL"><strong>MM_THEMECACHE_URL</strong></dt>
            <dd>
              <p>
                Set the location of the already generated MythTV themecache directory that will be mounted
                as the MythtTV themecache directory ('/home/minimyth/.mythtv/cache/themecache').
                Valid values are URL, 'none' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value is 'none',
                then nothing will be mounted as the already generated MythTV themecache directory.
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will assume that the MythTV themecache directory is in a squashfs image file
                located in the MiniMyth2 read-write configuration directory and
                having the name "themecache.sfs".
                That is, MiniMyth2 will assume MM_THEMECACHE_URL='confrw:themecache.sfs'.
              </p>
              <p>
                The MythTV frontend menus contain the 'Minimyth&nbsp;Tools' menu
                (under the 'Utilities&nbsp;/&nbsp;Setup' menu in a regular theme and under the main menu in a classic theme).
                The 'Minimyth&nbsp;Tools' menu contains the menu item 'Save&nbsp;Themecache'
                to help with creating a themecache squashfs image (themecache.sfs).
                The 'Save&nbsp;Themecache' menu item does the following:
              </p>
              <ol>
                <li>creates the themecache squashfs image from the one cached theme in the themecache directory, and</li>
                <li>saves the themecache squashfs image in the
                  <a href="document-configure.html#location">MiniMyth2 read-write configuration directory</a>.</li>
              </ol>
              <p>
                During the time that it takes MiniMyth2 to create and save the themecache squashfs image,
                MiniMyth2 will display a OSD notifications with status informations.
              </p>
              <p>
                The name of the themecache squashfs image will be themecache.sfs
              </p>
            </dd>
            <dt id="MM_THEME_FILE_MENU_ADD"><strong>MM_THEME_FILE_MENU_ADD</strong></dt>
            <dd>
              <p>
                Set a colon (':') separated list of theme menu files that will override/extend MythTV theme menus.
                These files will be copied from the MiniMyth2 read-only configuration directory.
              </p>
              <p>
                You can use this variable to do things such as change the frontend's menu structure
                by overriding the XML files that define the menu structure.
              </p>
            </dd>
          </dl>
          <p>
            Alternatively, you can mount the theme directories by adding the appropriate commands to the 'minimyth.script' package.
          </p>
        </div>
        <div id="MM_MEDIA" class="section">
          <div class="heading">Configuration variables for: remote media directories</div>
          <ul>
            <li><a href="#MM_MEDIA-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MEDIA_GAME_MOUNTPOINT">MM_MEDIA_GAME_MOUNTPOINT</a></li>
            <li><a href="#MM_MEDIA_GAME_URL">MM_MEDIA_GAME_URL</a></li>
            <li><a href="#MM_MEDIA_GENERIC_LIST">MM_MEDIA_GENERIC_LIST</a></li>
            <li><a href="#MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT">MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT</a></li>
            <li><a href="#MM_MEDIA_SCREENSAVER_GALLERY_URL">MM_MEDIA_SCREENSAVER_GALLERY_URL</a></li>
            <li><a href="#MM_MEDIA_AUDIO_RIP_URL">MM_MEDIA_AUDIO_RIP_URL</a></li>
          </ul>
          <dl>
            <dt id="MM_MEDIA-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                You can mount remote media directories by setting some variables.
              </p>
              <p>
                The URLs in this section must have the form described in the
                <a href="#MM_EXTRAS">Extras directory ...</a>
                section.
              </p>
            </dd>
            <dt id="MM_MEDIA_GALLERY_MOUNTPOINT"><strong>MM_MEDIA_GALLERY_MOUNTPOINT</strong></dt>
            <dd>
              <p>
                Set the location on the MiniMyth2 frontend's file system where
                '<a href="#MM_MEDIA_GALLERY_URL">MM_MEDIA_GALLERY_URL</a>'
                will be mounted.
                The default value is '/mnt/gallery'.
              </p>
            </dd>
            <dt id="MM_MEDIA_GALLERY_URL"><strong>MM_MEDIA_GALLERY_URL</strong></dt>
            <dd>
              <p>
                Set the URL that points to the location of the media for MythGallery.
                This will be mounted at
                '<a href="#MM_MEDIA_GALLERY_MOUNTPOINT">MM_MEDIA_GALLERY_MOUNTPOINT</a>'.
              </p>
            </dd>
            <dt id="MM_MEDIA_GAME_MOUNTPOINT"><strong>MM_MEDIA_GAME_MOUNTPOINT</strong></dt>
            <dd>
              <p>
                Set the location on the MiniMyth2 frontend's file system where
                '<a href="#MM_MEDIA_GAME_URL">MM_MEDIA_GAME_URL</a>'
                will be mounted.
                The default value is '/mnt/game'.
              </p>
            </dd>
            <dt id="MM_MEDIA_GAME_URL"><strong>MM_MEDIA_GAME_URL</strong></dt>
            <dd>
              <p>
                Set the URL that points to the location of the media for MythGame.
                This will be mounted at
                '<a href="#MM_MEDIA_GAME_MOUNTPOINT">MM_MEDIA_GAME_MOUNTPOINT</a>'.
              </p>
            </dd>
            <dt id="MM_MEDIA_GENERIC_LIST"><strong>MM_MEDIA_GENERIC_LIST</strong></dt>
            <dd>
              <p>
                A space separated list of {mountpoint}={url} values.
                If you have media shares that cannot be mounted using the MM_MEDIA_*_MOUNTPOINT + MM_MEDIA_*_URL pairs,
                then include them in this list and MiniMyth2 will mount them after mounting all shares specified by the
                MM_MEDIA_*_MOUNTPOINT + MM_MEDIA_*_URL pairs.
                The user 'minimyth' must have read access to the directory specified by {url}.
              </p>
            </dd>
            <dt id="MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT"><strong>MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT</strong></dt>
            <dd>
              <p>
                Set the location on the MiniMyth2 frontend's file system where
                pictures for screensaver glslideshow are located.
                The default value is '/mnt/screensaver'.
              </p>
            </dd>
            <dt id="MM_MEDIA_SCREENSAVER_GALLERY_URL"><strong>MM_MEDIA_SCREENSAVER_GALLERY_URL</strong></dt>
            <dd>
              <p>
                Set the URL that points to the location of the pictures displayed by screensaver (when enabled).
                This will be mounted at
                '<a href="#MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT">MM_MEDIA_SCREENSAVER_GALLERY_MOUNTPOINT</a>'.
              </p>
            </dd>
            <dt id="MM_MEDIA_AUDIO_RIP_URL"><strong>MM_MEDIA_AUDIO_RIP_URL</strong></dt>
            <dd>
              <p>
                Set the URL that points to the location of the temporary dir for holding temp. CD-Audio ripped files.
                This will be mounted at /home/minimyth/.mythtv/tmp/RipTemp
              </p>
            </dd>
          </dl>
          <p>
            Alternatively, you can mount remote directories by adding the appropriate commands to the 'minimyth.script' package.
            If you do this, there are some things that you should know.
          </p>
          <p>
            First, it is suggested that you create new mount points below '/mnt'.
          </p>
          <p>
            Second, there is a Minimyth.script function called 'mount_url' that you might find useful.
            This function takes two arguments:
          </p>
          <dl>
            <dt>url: required argument:</dt>
            <dd>This argument is described above.</dd>
            <dt>mount_dir: required argument:</dt>
            <dd>The local directory (e.g. /mnt/music) where the URL will be mounted.</dd>
          </dl>
        </div>
        <div id="MM_GAME" class="section">
          <div class="heading">Configuration variables for: games</div>
          <ul>
            <li><a href="#MM_GAME-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_GAME_SAVE_ENABLED">MM_GAME_SAVE_ENABLED</a></li>
            <li><a href="#MM_GAME_SAVE_LIST">MM_GAME_SAVE_LIST</a></li>
            <li><a href="#MM_GAME_BIOS_ROOT">MM_GAME_BIOS_ROOT</a></li>
            <li><a href="#MM_GAME_GAME_ROOT">MM_GAME_GAME_ROOT</a></li>
          </ul>
          <dl>
            <dt id="MM_GAME-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Game related configuration variables.
              </p>
            </dd>
            <dt id="MM_GAME_SAVE_ENABLED"><strong>MM_GAME_SAVE_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable saving of game settings.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                MythGame uses third party game console emulators to enable the user to play different games.
                Each game console emulator has its own method for configuration and its own set of configuration files.
                In addition, many of the game console emulators can save game state.
                However, unless this is saved somewhere other than your MiniMyth2 frontend, it will not survive reboot.
              </p>
              <p>
                If you set MM_GAME_SAVE_ENABLED='yes',
                then MiniMyth2 will save the game settings 'game.tar' in the
                <a href="document-configure.html#location">MiniMyth2 read-write configuration directory</a>
                during shut down
                and will restore the game settings from 'game.gar' during start up.
                Also, if you set MM_GAME_SAVE_ENABLED='yes' and you are running the game emulator using 'mm_game_start',
                then MiniMyth2 will save the game settings 'game.tar' in the
                <a href="document-configure.html#location">MiniMyth2 read-write configuration directory</a>
                on game emulator exit.
              </p>
              <p>
                In addition, the MythTV frontend menus contain the 'Minimyth&nbsp;Tools' menu
                (under the 'Utilities&nbsp;/&nbsp;Setup' menu in a regular theme and under the main menu in a classic theme).
                The 'Minimyth&nbsp;Tools' menu contains the menu items
                'Save&nbsp;Game&nbsp;Settings' and 'Restore&nbsp;Game&nbsp;Settings'
                to manually save and restore the game settings.
                During the time that it takes MiniMyth2 to save or restore the game settings
                MiniMyth2 will display a terminal window with status information.
              </p>
            </dd>
            <dt id="MM_GAME_SAVE_LIST"><strong>MM_GAME_SAVE_LIST</strong></dt>
            <dd>
              <p>
                Set a colon (':') separated list of game directories and files that will be saved and restored.
                All directories and files are relative to the home directory ('/home/minimyth').
                The default is a reasonable list based on the game emulators included in MiniMyth2.
              </p>
            </dd>
            <dt id="MM_GAME_BIOS_ROOT"><strong>MM_GAME_BIOS_ROOT</strong></dt>
            <dd>
              <p>
                Set the root of the directory tree containing the game console BIOS files.
                The default is "${<a href="#MM_MEDIA_GAME_MOUNTPOINT">MM_MEDIA_GAME_MOUNTPOINT</a>}/mnt/game/bios".
              </p>
              <p>
                MiniMyth2 expects the BIOS files for the game console '{console}'
                to be in the direcotry "${MM_GAME_BIOS_ROOT}/{console}".
                Example values for '{console}' are:
              </p>
              <ul>
                <li>a2600 - Atari 2600,</li>
                <li>cgb - Color Game Boy,</li>
                <li>gb - Game Boy,</li>
                <li>gba - Game Boy Advance,</li>
                <li>intv - Intellivision,</li>
                <li>nes - Nintendo Entertainment System, and</li>
                <li>snes - Super Nintendo Entertainment System.</li>
              </ul>
              <p>
                However, depending on the included game console emulators, other values may be needed.
              </p>
            </dd>
            <dt id="MM_GAME_GAME_ROOT"><strong>MM_GAME_GAME_ROOT</strong></dt>
            <dd>
              <p>
                Set the root of the directory tree containing the game console game files.
                The default is "${<a href="#MM_MEDIA_GAME_MOUNTPOINT">MM_MEDIA_GAME_MOUNTPOINT</a>}/game".
              </p>
              <p>
                MiniMyth2 expects the game files for the game console '{console}'
                to be in the directory "${MM_GAME_GAME_ROOT}/{console}".
                Example values for '{console}' are:
              </p>
              <ul>
                <li>a2600 - Atari 2600,</li>
                <li>cgb - Color Game Boy,</li>
                <li>gb - Game Boy,</li>
                <li>gba - Game Boy Advance,</li>
                <li>intv - Intellivision,</li>
                <li>nes - Nintendo Entertainment System, and</li>
                <li>snes - Super Nintendo Entertainment System.</li>
              </ul>
              <p>
                However, depending on the included game console emulators, other values may be needed.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_LIRC" class="section">
          <div class="heading">Configuration variables for: LIRC</div>
          <ul>
            <li><a href="#MM_LIRC-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_LIRC_USE_DEVINPUT">MM_LIRC_USE_DEVINPUT</a></li>
            <li><a href="#MM_LIRC_IREXEC_ENABLED">MM_LIRC_IREXEC_ENABLED</a></li>
            <li><a href="#MM_LIRC_IRXEVENT_ENABLED">MM_LIRC_IRXEVENT_ENABLED</a></li>
            <li><a href="#MM_LIRC_SLEEP_ENABLED">MM_LIRC_SLEEP_ENABLED</a></li>
            <li><a href="#MM_LIRC_WAKEUP_ENABLED">MM_LIRC_WAKEUP_ENABLED</a></li>
            <li><a href="#MM_LIRC_FETCH_OPTIONS_CONF">MM_LIRC_FETCH_OPTIONS_CONF</a></li>
            <li><a href="#MM_LIRC_FETCH_LIRCD_CONF">MM_LIRC_FETCH_LIRCD_CONF</a></li>
            <li><a href="#MM_LIRC_FETCH_IRBLASTER_CONF">MM_LIRC_FETCH_IRBLASTER_CONF</a></li>
            <li><a href="#MM_LIRC_FETCH_LIRCRC">MM_LIRC_FETCH_LIRCRC</a></li>
            <li><a href="#MM_LIRC_FETCH_EVMAP_CONF">MM_LIRC_FETCH_EVMAP_CONF</a></li>
          </ul>
          <dl>
            <dt id="MM_LIRC-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                MiniMyth2 uses
                <a href="www.lirc.org">LIRC</a>
                to enable the control of MiniMyth2 applications using a remote control.
                <a href="www.lirc.org">LIRC</a>
                supports many remote control receivers and remote controls,
                each of which require different configuration.
                In addition, in the case of remote control receivers connected using serial,
                configuration depends which serial port on your computer you use.
              </p>
              <p>
                If you are using a remote control receiver that connects using USB,
                then MiniMyth2 attempts to auto-detect the remote control receiver.
                However, if MiniMyth2 is not able to auto-detect your remote control receiver or remote control,
                then you can configure them using the LIRC configuration variables.
              </p>
            </dd>
            <dt id="MM_LIRC_USE_DEVINPUT"><strong>MM_LIRC_USE_DEVINPUT</strong></dt>
            <dd>
              <p>
                Indicate whether or not LIRC subsystem will use kernel devinput as input subsystem.
                Valid values are 'yes' and 'no' with 'yes' the default.
              </p>
              <p>
                If the value is 'yes', then MiniMyth2 will use kernel's IR protocol decoders, IR remotes key mappings and
                lircrc files adjusted to kernel IR remote name space. Benefit of using devinput is that any IR remote 
                supported by kernel is automatically avaliable for MiniMyth2 without any configuration.
                NOTE: kernel's devinput subsytem not supports IR Blaster - so if You want to use irbalster - devinput must be
                disabled. MiniMyth2 will automatically disable devinput if any of <a href="#MM_EXTERNAL-overview">IR blaster</a>
                commands is enabled/defined. In such case MiniMyth2 will use build-in multiple IR remote definitions. If You have 
                IR remote not build-in support - You can enable MiniMyth2 to download Your own lircd.conf file with help of
                <a href="#MM_LIRC_FETCH_LIRCD_CONF">MM_LIRC_FETCH_LIRCD_CONF</a>variable.
              </p>
            </dd>
            <dt id="MM_LIRC_IREXEC_ENABLED"><strong>MM_LIRC_IREXEC_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not the irexec daemon runs.
                Valid values are 'yes', 'no' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value is 'auto',
                Then MiniMyth2 will enable or disable the irexec daemon depending on whether irexec is
                used or not used in the lircrc file.
              </p>
            </dd>
            <dt id="MM_LIRC_IRXEVENT_ENABLED"><strong>MM_LIRC_IRXEVENT_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not the irxevent daemon runs.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                If the value is 'auto',
                Then MiniMyth2 will enable or disable the irxevent daemon depending on whether irxevent is
                used or not used in the lircrc file.
              </p>
            </dd>
            <dt id="MM_LIRC_SLEEP_ENABLED"><strong>MM_LIRC_SLEEP_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not the remote control's power button is used to put the frontend into S3 sleep
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                Before entering sleep,
                MiniMyth2 will attempt to
                exit game emulators (if running) and
                return to the MythTV frontend's main menu.
                MiniMyth2 relies on the 'Main Menu' JumpPoint in order to return to the MythTV frontend's main menu.
              </p>
              <p>
                Whether or not S3 sleep and wakeup work correctly depends on the motherboard's BIOS as well as
                the kernel and xorg drivers used by the frontend.
              </p>
            </dd>
            <dt id="MM_LIRC_WAKEUP_ENABLED"><strong>MM_LIRC_WAKEUP_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not the the remote control's power button is used to wake up the frontend from S3 sleep.
                Valid values are 'yes' and 'no', with 'yes' the default.
              </p>
              <p>
                Whether or not S3 sleep and wakeup work correctly depends on the motherboard's BIOS as well as
                the kernel and xorg drivers used by the frontend.
              </p>
              <p>
                This function assumes that the remote receiver uses the lirc_dev driver,
                creates a device /dev/lircN,
                and connects using USB.
                In addition, it assumes the motherboard supports USB wakeup from S3 sleep
                that has been enabled using the appropriate motherboard BIOS settings and/or motherboard jumper positions.
              </p>
            </dd>
            <dt id="MM_LIRC_FETCH_OPTIONS_CONF"><strong>MM_LIRC_FETCH_OPTIONS_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the lirc_option.conf
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
            <dt id="MM_LIRC_FETCH_LIRCD_CONF"><strong>MM_LIRC_FETCH_LIRCD_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#lircd_conf">lircd.conf</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                MiniMyth2 includes a limited number of
                '<a href="document-configure.html#lircd_conf">lircd.conf</a>'
                files.
                If MiniMyth2 does not contain an
                '<a href="document-configure.html#lircd_conf">lircd.conf</a>'
                file for your receiver+remote combination,
                then you will need to provide one in order for your remote control to work with MiniMyth2.
              </p>
              <p>
                MiniMyth2's LIRC configuration files follow the proposed
                <a href="http://arnaud.quette.free.fr/lirc/lirc-nns.html">LIRC namespace</a>.
                Therefore,
                if you provide an
                '<a href="document-configure.html#lircd_conf">lircd.conf</a>'
                that conforms to this namespace,
                then it should work with MiniMyth2's included
                '<a href="document-configure.html#lircrc">lircrc</a>'
                file.
              </p>
              <p>
                Currently includes support for the following receiver+remote combinations:
              </p>
              <ul>
                <li>an 'atiusb' receiver with various remotes</li>
                <li>a 'dvico' receiver with various remotes</li>
                <li>an 'irman' receiver with a 'hauppauge_A415' remote</li>
                <li>an 'irman' receiver with a 'hauppauge_R808' remote</li>
                <li>an 'mceusb' receiver with an 'mceusb' remote</li>
                <li>an 'mceusb2' receiver with an 'mceusb2' remote</li>
                <li>an 'serial' receiver with a 'hauppauge_R808' remote</li>
                <li>a 'streamzap' receiver with a 'streamzap' remote</li>
              </ul>
            </dd>
            <dt id="MM_LIRC_FETCH_IRBLASTER_CONF"><strong>MM_LIRC_FETCH_IRBLASTER_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#lircd_conf">lircd-irblaster.conf</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                MiniMyth2 includes a limited number of
                '<a href="document-configure.html#lircd_conf">lircd-irblaster.conf</a>'
                files.
                If MiniMyth2 does not contain an
                '<a href="document-configure.html#lircd_conf">lircd-irbaster.conf</a>'
                file for your irblaster controlled external equippment,
                then you will need to provide one in order for your external equipment to be controlled by MiniMyth2.
              </p>
              <p>
                MiniMyth2 currently includes support for the following external equipment:
              </p>
              <ul>
                <li>Samsung LCD TV UE40C5000 (this config should cover majority of Samsung TVs)</li>
                <li>Sharp LCD TV 46X20 (this config should cover majority of Sharp TVs)</li>
                <li>Sony STR940 aplituner</li>
              </ul>
            </dd>
            <dt id="MM_LIRC_FETCH_LIRCRC"><strong>MM_LIRC_FETCH_LIRCRC</strong></dt>
            <dd>
              <p>
                Inidicate whether or not to fetch the
                '<a href="document-configure.html#lircrc">lircrc</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
              <p>
                MiniMyth2 includes a general
                '<a href="document-configure.html#lircrc">lircrc</a>'
                as well as extensions to the general
                '<a href="document-configure.html#lircrc">lircrc</a>'
                for specific remote controls.
                If you do not like the mapping provided by the included
                '<a href="document-configure.html#lircrc">lircrc</a>'
                files,
                then you can provide your own.
              </p>
              <p>
                If MM_LIRC_FETCH_LIRCRC is set to "no", MiniMyth2 will use build-in
                lircrc file and also will defaulting some mythtv jumppoints. This is needed
                for proper and consistent remote keymappings to major mythtv functions like 
                watching LiveTV, listen music, etc. Following jumppoints will be set automatically
                by MiniMyth2:
                <li>Main Menu              ->  Alt+h</li>
                <li>Program Guide          ->  Alt+e</li>
                <li>Program Finder         ->  Alt+f</li>
                <li>TV Recording Playback  ->  Alt+r</li>
                <li>Live TV                ->  Alt+t</li>
                <li>Status Screen          ->  Alt+i</li>
                <li>MythGallery            ->  Alt+p</li>
                <li>MythGame               ->  Alt+g</li>
                <li>Play music             ->  Alt+m</li>
                <li>MythNews               ->  Alt+n</li>
                <li>MythVideo              ->  Alt+v</li>
                <li>Play radio stream      ->  Alt+s</li>
                <li>MythWeather            ->  Alt+w</li>
                <li>ZoneMinder Events      ->  Alt+z</li>
                <li>MythNetSearch          ->  Alt+a</li>
                <li>Toggle OSD playback info ->  Ctrl+v</li>
              </p>
            </dd>
            <dt id="MM_LIRC_FETCH_EVMAP_CONF"><strong>MM_LIRC_FETCH_EVMAP_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the eventlircd evmap file
                from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are empty and 'filename.evmao', with empty the default.
                Downloaed file will placed in /etc/eventlircd.d directory.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_LCDPROC" class="section">
          <div class="heading">Configuration variables for: LCDproc</div>
          <ul>
            <li><a href="#MM_LCDPROC-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_LCDPROC_ENABLED">MM_LCDPROC_ENABLED</a></li>
            <li><a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a></li>
            <li><a href="#MM_LCDPROC_DEVICE">MM_LCDPROC_DEVICE</a></li>
            <li><a href="#MM_LCDPROC_KERNEL_MODULE">MM_LCDPROC_KERNEL_MODULE</a></li>
            <li><a href="#MM_LCDPROC_KERNEL_MODULE_OPTIONS">MM_LCDPROC_KERNEL_MODULE_OPTIONS</a></li>
            <li><a href="#MM_LCDPROC_FETCH_LCDD_CONF">MM_LCDPROC_FETCH_LCDD_CONF</a></li>
          </ul>
          <dl>
            <dt id="MM_LCDPROC-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                MiniMyth2 uses
                <a href="http://lcdproc.omnipotent.net/">LCDproc</a>
                to enable MiniMyth2 to display information on a
                <a href="http://en.wikipedia.org/wiki/Liquid_crystal_display">Liquid Crystal Display (LCD)</a>
                or
                <a href="http://en.wikipedia.org/wiki/Vacuum_fluorescent_display">Vacuum Fluorescent Display (VFD)</a>,
                which can be mounted in one of the computer case's front mount drive bays.
                <a href="http://lcdproc.omnipotent.net/">LCDproc</a>
                supports many LCDs and VFDs,
                each of which require different configuration.
              </p>
              <p>
                If you are using an LCD or VFD that connects using USB,
                then MiniMyth2 attempts to auto-detect the LCD or VFD.
                However, if MiniMyth2 is not able to auto-detect your LCD or VFD,
                then you can configure it using the LCDproc configuration variables.
              </p>
            </dd>
            <dt id="MM_LCDPROC_ENABLED"><strong>MM_LCDPROC_ENABLED</strong></dt>
            <dd>
              <p>
                Enable LCDPROC in MiniMyth2. Valid values are 'no' and 'yes', with 'no' the default.
              </p>
            <dt id="MM_LCDPROC_DRIVER"><strong>MM_LCDPROC_DRIVER</strong></dt>
            <dd>
              <p>
                Set the name of the LCDd driver.
                Valid values are the name of the LCDd driver, 'none' and 'auto', with 'auto' the default'
                'MM_LCDPROC_DRIVER' is used to pick a driver specific built-in LCDd.conf file.
              </p>
              <p>
                If there is no driver specific build-in 'LCDd.conf' file for the LCDd driver,
                then the generic LCDd.conf file is used.
                Currently, there are no built-in 'LCDd.conf' files.
                If your LCD or VFD does not have a built-in 'LCDd.conf' file or
                you do not want to use the built-in 'LCDd.conf' file,
                then you can load your own 'LCDd.conf' using
                '<a href="#MM_LCDPROC_FETCH_LCDD_CONF">MM_LCDPROC_FETCH_LCDD_CONF</a>'.
              </p>
              <p>
                If the value is 'none,' then none will be picked.
              </p>
              <p>
                If the value is 'auto', then MiniMyth2 will attempt to auto-configure your LCD or VFD.
                If you use an LCD or VFD the connects using USB,
                then MiniMyth2 will attempt to determine the values for 'MM_LCDPROC_DRIVER' and
                '<a href="#MM_LCDPROC_DEVICE">MM_LCDPROC_DEVICE</a>'
                using the USB vendor and product identifiers in conjuction with the '/etc/hardware.d/usb2lcdproc.map' file.
                If your LCD or VFD is not auto-detected and you believe that it should have been auto-detected,
                then
                <a href="http://MiniMyth2.freeforums.org">let us know</a>
                the LCD or VFD vendor and model, the LCDproc driver used,
                the output of the command 'lsusb' with the LCD or VFD connected, and (if you have one)
                an 'LCDd.conf' file that works with MiniMyth2.
              </p>
            </dd>
            <dt id="MM_LCDPROC_DEVICE"><strong>MM_LCDPROC_DEVICE</strong></dt>
            <dd>
              <p>
                Set the name of your lirc device (e.g. '/dev/ttyS0').
                Valid values are the lirc device, 'none' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value of
                '<a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a>'
                is 'auto', then the value of MM_LCDPROC_DEVICE is ignored.
                Instead, MiniMyth2 uses the device associated with the auto-configured driver.
              </p>
              <p>
                If the value is 'none,' then no lirc device will be set.
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will attempt to pick a reasonable default value based on the value of
                '<a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a>'.
              </p>
            </dd>
            <dt id="MM_LCDPROC_KERNEL_MODULE"><strong>MM_LCDPROC_KERNEL_MODULE</strong></dt>
            <dd>
              <p>
                Set the name of any kernel module that you need to load to support your lirc device (e.g. '8250').
                Valid values are the kernel module, 'none' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value of
                '<a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a>'
                is 'auto' then MM_LCDPROC_KERNEL_MODULE is ignored.
                Instead, MiniMyth2 does not load any additional kernel modules.
              </p>
              <p>
                If the value is 'none,' then no lirc device will be set.
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will attempt to pick a reasonable default value based on the value of
                '<a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a>'.
              </p>
            </dd>
            <dt id="MM_LCDPROC_KERNEL_MODULE_OPTIONS"><strong>MM_LCDPROC_KERNEL_MODULE_OPTIONS</strong></dt>
            <dd>
              <p>
                Set the options for the kernel module specified by
                <a href="#MM_LCDPROC_KERNEL_MODULE">MM_LCDPROC_KERNEL_MODULE</a>.
                Valid values are the kernel module options, 'none' and 'auto', with 'auto' the default.
              </p>
              <p>
                If the value of
                '<a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a>'
                is 'auto' then MM_LCDPROC_KERNEL_MODULE_DRIVERS is ignored.
              </p>
              <p>
                If the value is 'none,' then no lirc device will be set.
              </p>
              <p>
                If the value is 'auto',
                then MiniMyth2 will attempt to pick a reasonable default value based on the value of
                '<a href="#MM_LCDPROC_DRIVER">MM_LCDPROC_DRIVER</a>'.
              </p>
            </dd>
            <dt id="MM_LCDPROC_FETCH_LCDD_CONF"><strong>MM_LCDPROC_FETCH_LCDD_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the
                '<a href="document-configure.html#LCDd_conf">LCDd.conf</a>'
                file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
          </dl>
          <p>
            Alternatively, you can configure LCDproc by adding the appropiate commands to 'Minimyth.script' package.
            If the 'lcdproc' init script detects that LCDd is already running, then it will exit immediately.
          </p>
        </div>
        <div id="MM_EXTERNAL" class="section">
          <div class="heading">Configuration variables for: external equipment control</div>
          <ul>
            <li><a href="#MM_EXTERNAL-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_EXTERNAL_POWER_OFF">MM_EXTERNAL_POWER_OFF</a></li>
            <li><a href="#MM_EXTERNAL_POWER_ON">MM_EXTERNAL_POWER_ON</a></li>
            <li><a href="#MM_EXTERNAL_VOLUME_DOWN">MM_EXTERNAL_VOLUME_DOWN</a></li>
            <li><a href="#MM_EXTERNAL_VOLUME_UP">MM_EXTERNAL_VOLUME_UP</a></li>
            <li><a href="#MM_EXTERNAL_VOLUME_MUTE">MM_EXTERNAL_VOLUME_MUTE</a></li>
          </ul>
          <dl>
            <dt id="MM_EXTERNAL-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                External equipment control related configuration variables.
              </p>
            </dd>
            <dt id="MM_EXTERNAL_POWER_OFF"><strong>MM_EXTERNAL_POWER_OFF</strong></dt>
            <dd>
              <p>
                Set the command sequence MiniMyth2 should use when it needs to power off external equipment.
                Valid values are a ';' separated list of zero or more shell commands, with '' the default.
              </p>
              <p>
                This command sequence will be executed just before MiniMyth2 enters sleep.
              </p>
            </dd>
            <dt id="MM_EXTERNAL_POWER_ON"><strong>MM_EXTERNAL_POWER_ON</strong></dt>
            <dd>
              <p>
                Set the command sequence MiniMyth2 should use when it needs to power on external equipment.
                Valid values are a ';' separated list of zero or more shell commands, with '' the default.
              </p>
              <p>
                This command sequence will be executed just after MiniMyth2 leaves sleep.
              </p>
            </dd>
            <dt id="MM_EXTERNAL_VOLUME_DOWN"><strong>MM_EXTERNAL_VOLUME_DOWN</strong></dt>
            <dd>
              <p>
                Set the command sequence MiniMyth2 should use when it needs to turn down the volume using external equipment.
                Valid values are a ';' separated list of zero or more shell commands, with '' the default.
                If 'MM_EXTERNAL_VOLUME_DOWN is set, then
                <a href="#MM_EXTERNAL_VOLUME_UP">MM_EXTERNAL_VOLUME_UP</a>
                must be set.
              </p>
            </dd>
            <dt id="MM_EXTERNAL_VOLUME_UP"><strong>MM_EXTERNAL_VOLUME_UP</strong></dt>
            <dd>
              <p>
                Set the command sequence MiniMyth2 should use when it needs to turn up the volume using external equipment.
                Valid values are a ';' separated list of zero or more shell commands, with '' the default.
                If 'MM_EXTERNAL_VOLUME_UP' is set, then
                <a href="#MM_EXTERNAL_VOLUME_DOWN">MM_EXTERNAL_VOLUME_DOWN</a>
                must be set.
              </p>
            </dd>
            <dt id="MM_EXTERNAL_VOLUME_MUTE"><strong>MM_EXTERNAL_VOLUME_MUTE</strong></dt>
            <dd>
              <p>
                Set the command sequence MiniMyth2 should use when it needs to mute/unmute the volume using external equipment.
                Valid values are a ';' separated list of zero or more shell commands, with '' the default.
                If 'MM_EXTERNAL_VOLUME_MUTE' is set, then
                <a href="#MM_EXTERNAL_VOLUME_DOWN">MM_EXTERNAL_VOLUME_DOWN</a>
                and
                <a href="#MM_EXTERNAL_VOLUME_UP">MM_EXTERNAL_VOLUME_UP</a>
                must be set.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_SSH_SERVER" class="section">
          <div class="heading">Configuration variables for: SSH server</div>
          <ul>
            <li><a href="#MM_SSH_SERVER-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_SSH_SERVER_ENABLED">MM_SSH_SERVER_ENABLED</a></li>
          </ul>
          <dl>
            <dt id="MM_SSH_SERVER-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                MiniMyth2 supports running an SSH server.
                If you are not securing the MiniMyth2 frontend, then there is little reason to run an SSH server.
                However, if you are securing the frontend, then using an SSH server rather than a telnet server
                will provide secure access to the frontend.
              </p>
              <p>
                The SSH server is configured such that it allows only public key authentication.
              </p>
              <p>
                If you decide to enable the SSH server, be sure that you know what you are doing.
                Since the TFTP server's access is not secure,
                when you are network booting,
                you should assume that anything with access to your network has access the SSH private RSA identity file
                and can impersonate the SSH server.
                Therefore, when you are network booting,
                you should not assume that an SSH server using this identity file is your SSH server.
              </p>
            </dd>
            <dt id="MM_SSH_SERVER_ENABLED"><strong>MM_SSH_SERVER_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not you want to enable MiniMyth2's SSH server.
                Valid values are 'yes' and 'no',
                with 'yes' the default when '<a href="#MM_SECURITY_ENABLED">MM_SECURITY_ENABLED</a>' is 'yes', and
                with 'no' the default when '<a href="#MM_SECURITY_ENABLED">MM_SECURITY_ENABLED</a>' is not 'yes'.
              </p>
              <p>
                When the SSH is enabled,
                MiniMyth2 will attempt to fetch the
                '<a href="document-configure.html#ssh_host_rsa_key">ssh_host_rsa_key</a>'
                and
                '<a href="document-configure.html#authorized_keys">authorized_keys</a>'
                files from the frontend's MiniMyth2 read-only configuration directory.
                If it fails to fetch either file, then it will generate an error.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_CRON" class="section">
          <div class="heading">Configuration variables for: cron</div>
          <ul>
            <li><a href="#MM_CRON-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_CRON_FETCH_CRONTAB">MM_CRON_FETCH_CRONTAB</a></li>
          </ul>
          <dl>
            <dt id="MM_CRON-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Cron related configuration variables.
              </p>
            </dd>
            <dt id="MM_CRON_FETCH_CRONTAB"><strong>MM_CRON_FETCH_CRONTAB</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the 'crontab' file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_MYTHDB" class="section">
          <div class="heading">Configuration variables for: Myth frontend</div>
          <ul>
            <li><a href="#MM_MYTHDB-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_MYTHDB_JUMPPOINTS">MM_MYTHDB_JUMPPOINTS_{key}</a></li>
            <li><a href="#MM_MYTHDB_KEYBINDINGS">MM_MYTHDB_KEYBINDINGS_{key}</a></li>
            <li><a href="#MM_MYTHDB_SETTINGS">MM_MYTHDB_SETTINGS_{key}</a></li>
          </ul>
          <dl>
            <dt id="MM_MYTHDB-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Based on settings in other sections, MiniMyth2 changes the Myth frontend settings in the Myth database.
                However, if you want MiniMyth2 to change other Myth frontend settings in the Myth database
                (or you want to override the changes made by MiniMyth2 as a result of seeting in other sections),
                then you can use the Myth frontend configuration variables.
              </p>
            </dd>
            <dt id="MM_MYTHDB_JUMPPOINTS"><strong>MM_MYTHDB_JUMPPOINTS_{key}</strong></dt>
            <dd>
              <p>
                Myth frontend jumppoints are stored in the 'jumppoints' table in the MythTV master backend database.
                MiniMyth2 can modify its jumppoints in the 'jumppoints' table.
                The variables are set as follows:
              </p>
              <p>
                MM_MYTHDB_JUMPPOINTS_{key}='{destination}~{keylist}'
                One possible value to use for the key is {destination}.
              </p>
              <p>
                The {key} is added to ensure that each jumppoint variable has a unique name.
                Therefore, you must choose a different value of {key} for each jumppoint variable.
              </p>
            </dd>
            <dt id="MM_MYTHDB_KEYBINDINGS"><strong>MM_MYTHDB_KEYBINDINGS_{key}</strong></dt>
            <dd>
              <p>
                Myth frontend keybindings are stored in the 'keybindings' table in the MythTV master backend database.
                MiniMyth2 can modify its keybindings in the 'keybindings' table.
                The variables are set as follows:
              </p>
              <p>
                MM_MYTHDB_KEYBINDINGS_{key}='{context}~{action}~{keylist}'
              </p>
              <p>
                The {key} is added to ensure that each keybinding variable has a unique name.
                Therefore, you must choose a different value of {key} for each keybinding variable.
                One possible value to use for the key is {context}_{action}.
              </p>
            </dd>
            <dt id="MM_MYTHDB_SETTINGS"><strong>MM_MYTHDB_SETTINGS_{key}</strong></dt>
            <dd>
              <p>
                Myth frontend settings are stored in the 'settings' table in the MythTV master backend database.
                MiniMyth2 can modify its settings in the 'settings' table.
                The variables are set as follows:
              </p>
              <p>
                MM_MYTHDB_SETTINGS_{key}='{value}~{data}'
              </p>
              <p>
                The {key} is added to ensure that each setting variable has a unique name.
                Therefore, you must choose a different value of {key} for each setting variable.
                One possible value to use for the key is {value}.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_LMSENSORS" class="section">
          <div class="heading">Configuration variables for: lmsensors</div>
          <ul>
            <li><a href="#MM_LMSENSORS-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_LMSENSORS_FETCH_CONF">MM_LMSENSORS_FETCH_CONF</a></li>
          </ul>
          <dl>
            <dt id="MM_LMSENSORS-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                lmsensors related configuration variables.
              </p>
            </dd>
            <dt id="MM_LMSENSORS_FETCH_CONF"><strong>MM_LMSENSORS_FETCH_CONF</strong></dt>
            <dd>
              <p>
                Indicate whether or not to fetch the 'sensors3.conf' file from the frontend's MiniMyth2 read-only configuration directory.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_MAKEMKV" class="section">
          <div class="heading">Configuration variables for: Optical discs Ripping/Copy</div>
          <ul>
            <li><a href="#MM_MAKEMKV-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_OPTICAL_RIP_ENABLED">MM_OPTICAL_RIP_ENABLED</a></li>
          </ul>
          <ul>
            <li><a href="#MM_OPTICAL_RIP_URL">MM_OPTICAL_RIP_URL</a></li>
          </ul>
          <ul>
            <li><a href="#MM_OPTICAL_DISC_ID">MM_OPTICAL_DISC_ID</a></li>
          </ul>
          <dl>
            <dt id="MM_MAKEMKV-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Minimyh2 has build-in excellent MakeMKV program allowing real-time decrypting BluRay discs for
                watching. MakeMKV also allows to simple rip/copy BluRay/DVD discs. This section describes optical 
                rip/copy related configuration variables.
              </p>
            </dd>
            <dt id="MM_OPTICAL_RIP_ENABLED"><strong>MM_OPTICAL_RIP_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable optical discs Rip/Copy feature. If set to 'Yes', then MiniMyth2 will
                add to Optical Disc submenu entries for: 'Rip', 'Copy', 'ShowProgress' and 'Stop'. Enabling this option
                requires also setting MM_OPTICAL_RIP_URL variable. Also MiniMyth2 will download makemkv.conf file from 
                conf-ro dir. This file is required by MakeMKV and should contain valid serial number. MiniMyth2 will also
                download binary file 'makemkvcon' which user should officially install in system accepting EULA. This binary
                (usually located in /usr/bin) should be sym-linked to MiniMyth2 conf-ro dir.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
            <dt id="MM_OPTICAL_RIP_URL"><strong>MM_OPTICAL_RIP_URL</strong></dt>
            <dd>
              <p>
                Indicate whether Rip/Copy process will store MKV files with ripped/copied disc content. Best solution is
                to devote subdir with 50GB of free space on server and point this variable to this dir. 
              </p>
            </dd>
            <dt id="MM_OPTICAL_DISC_ID"><strong>MM_OPTICAL_DISC_ID</strong></dt>
            <dd>
              <p>
                Indicate ID of optical disc used by MakeMKV process to Rip/Copy of optical discs. This variable is
                usefull when MiniMyth2 system has more than one optical drives and i.e. user one from them is BluRay drive
                used to watch/Rip/Copy Bluray/DVD mobvies.
                Valid values are 'number', with '0' the default.
              </p>
            </dd>
          </dl>
        </div>
        <div id="MM_VOIP" class="section">
          <div class="heading">Configuration variables for: VoIP telephony</div>
          <ul>
            <li><a href="#MM_VOIP-overview">Overview</a></li>
          </ul>
          <ul>
            <li><a href="#MM_VOIP_ENABLED">MM_VOIP_ENABLED</a></li>
          </ul>
          <ul>
            <li><a href="#MM_VOIP_LOAD_CONFIG">MM_VOIP_LOAD_CONFIG</a></li>
          </ul>
          <ul>
            <li><a href="#MM_VOIP_MIC_LEVEL">MM_VOIP_MIC_LEVEL</a></li>
          </ul>
          <ul>
            <li><a href="#MM_VOIP_BOOST_MIC_LEVEL">MM_VOIP_BOOST_MIC_LEVEL</a></li>
          </ul>
          <ul>
            <li><a href="#MM_VOIP_MIC_SELECTION">MM_VOIP_MIC_SELECTION</a></li>
          </ul>
          <dl>
            <dt id="MM_VOIP-overview"><strong>Overview</strong></dt>
            <dd>
              <p>
                Minimyh2 has build-in simple SIP VoIP telephony support. It allows to receive and make 
                SIP VoIP calls.
              </p>
            </dd>
            <dt id="MM_VOIP_ENABLED"><strong>MM_VOIP_ENABLED</strong></dt>
            <dd>
              <p>
                Indicate whether or not to enable SIP VoIP telephony feature. If set to 'Yes', then MiniMyth2 will
                add to mainmenu 'Telephony' submenu with phone entries for making calls.
                Valid values are 'yes' and 'no', with 'no' the default.
              </p>
            </dd>
            <dt id="MM_VOIP_LOAD_CONFIG"><strong>MM_VOIP_LOAD_CONFIG</strong></dt>
            <dd>
              <p>
                Indicate whether MiniMyth2 should load SIP config file from conf-ro dir. When enabled, MiniMyth2 will
                load 'sip-daemon.conf' file with SIP config and 'phone-book.xml' with simple phone book.
              </p>
            </dd>
            <dt id="MM_VOIP_MIC_LEVEL"><strong>MM_VOIP_MIC_LEVEL</strong></dt>
            <dd>
              <p>
                Indicate microphone level MiniMyth2 will set for VoIP calls.
                Valid values are: 'number', with '75' the default.
              </p>
            </dd>
            <dt id="MM_VOIP_MIC_BOOST_LEVEL"><strong>MM_VOIP_MIC_BOOST_LEVEL</strong></dt>
            <dd>
              <p>
                Indicate microphone boost level MiniMyth2 will set for VoIP calls.
                Valid values are: empty field, 'number', with empty as the default.
              </p>
            </dd>
            <dt id="MM_VOIP_MIC_SELECTION"><strong>MM_VOIP_MIC_SELECTION</strong></dt>
            <dd>
              <p>
                Indicate which microphone input (Mic Front, Mic Rear, etc) should be connected to 'Input Source 0'.
                If not set then selection is based on ALSA defaults. If set to 'string' ten MiniMyth2 will execute
                amixer -c<MM_AUDIO_IN_CARD_NUMBER> set 'Input Source’,0 'string'
                Valid values are: empty field, 'string', with empty as the default.
              </p>
            </dd>
          </dl>
        </div>
      </div>
      <div class="footer">
        <hr />
        <div class="valid-xhtml">
          <a href="http://validator.w3.org/check?uri=referer"><img
              src="/image/w3c-valid-xhtml11-blue.gif"
              alt="Valid XHTML 1.1" height="31" width="88" /></a>
        </div>
        <div class="valid-css">
          <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
              src="/image/w3c-valid-css2-blue.gif"
              alt="Valid CSS!"      height="31" width="88" /></a>
        </div>
        <div class="version">
          Last Updated on 2020-01-06
          <br />
          &lt;&nbsp;mailto&nbsp;:&nbsp;warpme&nbsp;at&nbsp;o2&nbsp;dot&nbsp;pl&nbsp;&gt;
        </div>
      </div>
    </div>
  </body>
</html>
